apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:40:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-45-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-45.ec2.internal
      uid: 1e71df03-c3b4-4208-8de7-f0d10e87f521
    resourceVersion: "20566"
    uid: f0af4e0e-2e5f-4634-8430-52acf81002d8
  spec:
    sourcePod: network-check-source-685456655f-bs7cf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T06:47:35Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 866.049µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:01:35Z"
    - latency: 1.279784ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:00:35Z"
    - latency: 1.054835ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:59:35Z"
    - latency: 959.666µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:58:35Z"
    - latency: 977.304µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:57:35Z"
    - latency: 1.023802ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:56:35Z"
    - latency: 1.349993ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:55:35Z"
    - latency: 1.143846ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:54:35Z"
    - latency: 1.086135ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:53:35Z"
    - latency: 1.003896ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:52:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:40:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-45-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-45.ec2.internal
      uid: 1e71df03-c3b4-4208-8de7-f0d10e87f521
    resourceVersion: "22215"
    uid: 16c38ae8-57d6-4e9a-95ae-37c0366229fb
  spec:
    sourcePod: network-check-source-685456655f-bs7cf
    targetEndpoint: a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T06:46:35Z"
      message: 'load-balancer-api-external: tcp connection to a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.173955ms
      message: 'load-balancer-api-external: tcp connection to a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:04:35Z"
    - latency: 8.046991ms
      message: 'load-balancer-api-external: resolved host name a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:04:35Z"
    - latency: 5.173598ms
      message: 'load-balancer-api-external: tcp connection to a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:03:35Z"
    - latency: 8.205534ms
      message: 'load-balancer-api-external: resolved host name a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:03:35Z"
    - latency: 5.601938ms
      message: 'load-balancer-api-external: tcp connection to a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:02:35Z"
    - latency: 8.773686ms
      message: 'load-balancer-api-external: resolved host name a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:02:35Z"
    - latency: 5.928334ms
      message: 'load-balancer-api-external: tcp connection to a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:01:35Z"
    - latency: 9.379115ms
      message: 'load-balancer-api-external: resolved host name a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:01:35Z"
    - latency: 3.337896ms
      message: 'load-balancer-api-external: tcp connection to a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:00:35Z"
    - latency: 6.228855ms
      message: 'load-balancer-api-external: resolved host name a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:00:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:40:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-45-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-45.ec2.internal
      uid: 1e71df03-c3b4-4208-8de7-f0d10e87f521
    resourceVersion: "22214"
    uid: 86ca24cf-f836-4763-a161-2da6edf80aa4
  spec:
    sourcePod: network-check-source-685456655f-bs7cf
    targetEndpoint: a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T06:46:35Z"
      message: 'load-balancer-api-internal: tcp connection to a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.138483ms
      message: 'load-balancer-api-internal: tcp connection to a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:04:35Z"
    - latency: 8.082912ms
      message: 'load-balancer-api-internal: resolved host name a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:04:35Z"
    - latency: 5.170956ms
      message: 'load-balancer-api-internal: tcp connection to a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:03:35Z"
    - latency: 8.161537ms
      message: 'load-balancer-api-internal: resolved host name a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:03:35Z"
    - latency: 5.749932ms
      message: 'load-balancer-api-internal: tcp connection to a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:02:35Z"
    - latency: 8.840084ms
      message: 'load-balancer-api-internal: resolved host name a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:02:35Z"
    - latency: 5.916857ms
      message: 'load-balancer-api-internal: tcp connection to a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:01:35Z"
    - latency: 9.426046ms
      message: 'load-balancer-api-internal: resolved host name a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:01:35Z"
    - latency: 3.319114ms
      message: 'load-balancer-api-internal: tcp connection to a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:00:35Z"
    - latency: 6.304318ms
      message: 'load-balancer-api-internal: resolved host name a7644483b774c4eaeb91d149230148be-332504f14c40bd3f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:00:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:40:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-45-to-network-check-target-ip-10-0-128-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-45.ec2.internal
      uid: 1e71df03-c3b4-4208-8de7-f0d10e87f521
    resourceVersion: "20562"
    uid: 486500c5-ea69-4f15-ae28-066399c5ddbd
  spec:
    sourcePod: network-check-source-685456655f-bs7cf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T06:47:35Z"
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 803.737µs
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:01:35Z"
    - latency: 952.583µs
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:00:35Z"
    - latency: 1.397842ms
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:59:35Z"
    - latency: 754.87µs
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:58:35Z"
    - latency: 813.587µs
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:57:35Z"
    - latency: 960.053µs
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:56:35Z"
    - latency: 776.8µs
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:55:35Z"
    - latency: 902.347µs
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:54:35Z"
    - latency: 1.519405ms
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:53:35Z"
    - latency: 681.767µs
      message: 'network-check-target-ip-10-0-128-45: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:52:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:40:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-45-to-network-check-target-ip-10-0-136-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-45.ec2.internal
      uid: 1e71df03-c3b4-4208-8de7-f0d10e87f521
    resourceVersion: "20565"
    uid: 70c080d6-06c9-41cc-a09d-5761af30ed13
  spec:
    sourcePod: network-check-source-685456655f-bs7cf
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T06:47:35Z"
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.386785ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:01:35Z"
    - latency: 2.494942ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:00:35Z"
    - latency: 2.441202ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:59:35Z"
    - latency: 3.149717ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:58:35Z"
    - latency: 2.33749ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:57:35Z"
    - latency: 2.665949ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:56:35Z"
    - latency: 2.777115ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:55:35Z"
    - latency: 3.149137ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:54:35Z"
    - latency: 2.636661ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:53:35Z"
    - latency: 2.112954ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:52:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:40:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-45-to-network-check-target-ip-10-0-138-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-45.ec2.internal
      uid: 1e71df03-c3b4-4208-8de7-f0d10e87f521
    resourceVersion: "20564"
    uid: 1839660d-88e3-4fc8-8a38-9d8c0801a0dc
  spec:
    sourcePod: network-check-source-685456655f-bs7cf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T06:47:35Z"
      message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.988968ms
      message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:01:35Z"
    - latency: 2.403882ms
      message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:00:35Z"
    - latency: 2.394632ms
      message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:59:35Z"
    - latency: 2.324807ms
      message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:58:35Z"
    - latency: 2.09528ms
      message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:57:35Z"
    - latency: 2.563396ms
      message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:56:35Z"
    - latency: 2.491208ms
      message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:55:35Z"
    - latency: 2.869649ms
      message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:54:35Z"
    - latency: 2.492182ms
      message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:53:35Z"
    - latency: 2.127193ms
      message: 'network-check-target-ip-10-0-138-193: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T06:52:35Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T06:40:34Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-45-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-45.ec2.internal
      uid: 1e71df03-c3b4-4208-8de7-f0d10e87f521
    resourceVersion: "22213"
    uid: fa2fd3cf-feb3-4702-b715-5ec2a7672aa3
  spec:
    sourcePod: network-check-source-685456655f-bs7cf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T06:46:35Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 827.363µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:04:35Z"
    - latency: 1.619033ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:04:35Z"
    - latency: 991.647µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:03:35Z"
    - latency: 1.636788ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:03:35Z"
    - latency: 1.223279ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:02:35Z"
    - latency: 1.912328ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:02:35Z"
    - latency: 753.914µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:01:35Z"
    - latency: 1.689982ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:01:35Z"
    - latency: 842.655µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T07:00:35Z"
    - latency: 1.560271ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T07:00:35Z"
kind: List
metadata:
  resourceVersion: ""