apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-112-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-112.ec2.internal
      uid: 7324d804-e42e-46b0-a6e4-d8646b0cd7f8
    resourceVersion: "54234"
    uid: 4b5f0012-be38-4d9d-90a9-4fe5edff4eb5
  spec:
    sourcePod: network-check-source-989f8b8dc-5t8dp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:30:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.199301ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:04Z"
    - latency: 1.087942ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:04Z"
    - latency: 826.495µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:04Z"
    - latency: 1.156273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:04Z"
    - latency: 904.641µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:04Z"
    - latency: 990.556µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:04Z"
    - latency: 1.030542ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:52:04Z"
    - latency: 941.842µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:51:04Z"
    - latency: 1.133283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:50:04Z"
    - latency: 1.020921ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:49:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-112-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-112.ec2.internal
      uid: 7324d804-e42e-46b0-a6e4-d8646b0cd7f8
    resourceVersion: "55242"
    uid: 53de12f2-9f34-45eb-9bd1-5f0ddae87e37
  spec:
    sourcePod: network-check-source-989f8b8dc-5t8dp
    targetEndpoint: ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:29:04Z"
      message: 'load-balancer-api-external: tcp connection to ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.025526ms
      message: 'load-balancer-api-external: tcp connection to ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:04Z"
    - latency: 6.658341ms
      message: 'load-balancer-api-external: resolved host name ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:59:04Z"
    - latency: 5.629896ms
      message: 'load-balancer-api-external: tcp connection to ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:04Z"
    - latency: 7.5681ms
      message: 'load-balancer-api-external: resolved host name ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:58:04Z"
    - latency: 4.317054ms
      message: 'load-balancer-api-external: tcp connection to ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:04Z"
    - latency: 7.347127ms
      message: 'load-balancer-api-external: resolved host name ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:57:04Z"
    - latency: 7.158725ms
      message: 'load-balancer-api-external: tcp connection to ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:04Z"
    - latency: 6.536504ms
      message: 'load-balancer-api-external: resolved host name ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:56:04Z"
    - latency: 4.196344ms
      message: 'load-balancer-api-external: tcp connection to ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:04Z"
    - latency: 6.665375ms
      message: 'load-balancer-api-external: resolved host name ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:55:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-112-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-112.ec2.internal
      uid: 7324d804-e42e-46b0-a6e4-d8646b0cd7f8
    resourceVersion: "55243"
    uid: 455d9a85-4141-4fd0-bed1-8fa771431ecf
  spec:
    sourcePod: network-check-source-989f8b8dc-5t8dp
    targetEndpoint: ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:29:04Z"
      message: 'load-balancer-api-internal: tcp connection to ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.099569ms
      message: 'load-balancer-api-internal: tcp connection to ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:04Z"
    - latency: 6.726276ms
      message: 'load-balancer-api-internal: resolved host name ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:59:04Z"
    - latency: 5.612688ms
      message: 'load-balancer-api-internal: tcp connection to ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:04Z"
    - latency: 7.456704ms
      message: 'load-balancer-api-internal: resolved host name ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:58:04Z"
    - latency: 5.82721ms
      message: 'load-balancer-api-internal: tcp connection to ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:04Z"
    - latency: 7.29964ms
      message: 'load-balancer-api-internal: resolved host name ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:57:04Z"
    - latency: 4.659273ms
      message: 'load-balancer-api-internal: tcp connection to ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:04Z"
    - latency: 6.509105ms
      message: 'load-balancer-api-internal: resolved host name ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:56:04Z"
    - latency: 4.607611ms
      message: 'load-balancer-api-internal: tcp connection to ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:04Z"
    - latency: 6.803566ms
      message: 'load-balancer-api-internal: resolved host name ae9a3c61cefc748a681a97e0e2287996-067862da6d9c7198.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:55:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-112-to-network-check-target-ip-10-0-133-112
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-112.ec2.internal
      uid: 7324d804-e42e-46b0-a6e4-d8646b0cd7f8
    resourceVersion: "54231"
    uid: a93c5ec7-c2a9-4842-ad28-3e6c833daa4c
  spec:
    sourcePod: network-check-source-989f8b8dc-5t8dp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:30:04Z"
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 877.648µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:04Z"
    - latency: 684.744µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:04Z"
    - latency: 804.004µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:04Z"
    - latency: 1.055658ms
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:04Z"
    - latency: 929.193µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:04Z"
    - latency: 1.333542ms
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:04Z"
    - latency: 963.789µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:52:04Z"
    - latency: 1.333555ms
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:51:04Z"
    - latency: 1.139353ms
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:50:04Z"
    - latency: 843.795µs
      message: 'network-check-target-ip-10-0-133-112: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:49:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-112-to-network-check-target-ip-10-0-135-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-112.ec2.internal
      uid: 7324d804-e42e-46b0-a6e4-d8646b0cd7f8
    resourceVersion: "54232"
    uid: 3601bfb7-3d7b-4d9b-b944-d191616f7935
  spec:
    sourcePod: network-check-source-989f8b8dc-5t8dp
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:30:04Z"
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.96421ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:04Z"
    - latency: 1.82308ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:04Z"
    - latency: 1.715183ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:04Z"
    - latency: 2.007693ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:04Z"
    - latency: 1.828466ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:04Z"
    - latency: 2.013386ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:04Z"
    - latency: 1.970795ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:52:04Z"
    - latency: 1.778983ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:51:04Z"
    - latency: 1.992698ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:50:04Z"
    - latency: 2.057344ms
      message: 'network-check-target-ip-10-0-135-124: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:49:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-112-to-network-check-target-ip-10-0-136-208
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-112.ec2.internal
      uid: 7324d804-e42e-46b0-a6e4-d8646b0cd7f8
    resourceVersion: "54233"
    uid: 52442456-65d0-45a2-88ae-2316ecfbcb30
  spec:
    sourcePod: network-check-source-989f8b8dc-5t8dp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:30:04Z"
      message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.315069ms
      message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:04Z"
    - latency: 2.383881ms
      message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:04Z"
    - latency: 1.932136ms
      message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:04Z"
    - latency: 2.312121ms
      message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:04Z"
    - latency: 1.990496ms
      message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:54:04Z"
    - latency: 2.278397ms
      message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:53:04Z"
    - latency: 1.829867ms
      message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:52:04Z"
    - latency: 2.16868ms
      message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:51:04Z"
    - latency: 2.299764ms
      message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:50:04Z"
    - latency: 2.570059ms
      message: 'network-check-target-ip-10-0-136-208: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:49:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T14:23:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-112-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-112.ec2.internal
      uid: 7324d804-e42e-46b0-a6e4-d8646b0cd7f8
    resourceVersion: "55241"
    uid: 2df2a832-773a-4c33-a51c-8c41810ea252
  spec:
    sourcePod: network-check-source-989f8b8dc-5t8dp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T14:29:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 987.951µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:59:04Z"
    - latency: 1.630159ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:59:04Z"
    - latency: 1.216377ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:58:04Z"
    - latency: 1.710198ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:58:04Z"
    - latency: 1.031078ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:57:04Z"
    - latency: 1.811235ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:57:04Z"
    - latency: 1.078371ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:56:04Z"
    - latency: 1.659909ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:56:04Z"
    - latency: 957.98µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:55:04Z"
    - latency: 1.50056ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:55:04Z"
kind: List
metadata:
  resourceVersion: ""