apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:19:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-211-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-211.ec2.internal
      uid: 73dbd4c3-66f8-4245-83d1-b436157f1b39
    resourceVersion: "52707"
    uid: 76ba0d48-503f-48f8-ab3e-c9c5faca0d84
  spec:
    sourcePod: network-check-source-685456655f-h9n7q
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:26:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.316518ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:47:59Z"
    - latency: 1.159324ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:46:59Z"
    - latency: 1.32607ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:45:59Z"
    - latency: 1.66191ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:44:59Z"
    - latency: 1.321639ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:43:59Z"
    - latency: 1.059931ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:42:59Z"
    - latency: 797.283µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:41:59Z"
    - latency: 1.426147ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:40:59Z"
    - latency: 1.221442ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:39:59Z"
    - latency: 882.903µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:38:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:19:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-211-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-211.ec2.internal
      uid: 73dbd4c3-66f8-4245-83d1-b436157f1b39
    resourceVersion: "54177"
    uid: e48365ad-3bfa-40de-a3be-acf5f853ede2
  spec:
    sourcePod: network-check-source-685456655f-h9n7q
    targetEndpoint: a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:25:59Z"
      message: 'load-balancer-api-external: tcp connection to a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.672381ms
      message: 'load-balancer-api-external: tcp connection to a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:49:59Z"
    - latency: 9.584303ms
      message: 'load-balancer-api-external: resolved host name a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:49:59Z"
    - latency: 5.474793ms
      message: 'load-balancer-api-external: tcp connection to a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:48:59Z"
    - latency: 8.909699ms
      message: 'load-balancer-api-external: resolved host name a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:48:59Z"
    - latency: 4.662369ms
      message: 'load-balancer-api-external: tcp connection to a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:47:59Z"
    - latency: 8.979781ms
      message: 'load-balancer-api-external: resolved host name a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:47:59Z"
    - latency: 5.459613ms
      message: 'load-balancer-api-external: tcp connection to a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:46:59Z"
    - latency: 8.100996ms
      message: 'load-balancer-api-external: resolved host name a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:46:59Z"
    - latency: 4.310678ms
      message: 'load-balancer-api-external: tcp connection to a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:45:59Z"
    - latency: 10.106482ms
      message: 'load-balancer-api-external: resolved host name a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:45:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:19:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-211-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-211.ec2.internal
      uid: 73dbd4c3-66f8-4245-83d1-b436157f1b39
    resourceVersion: "54178"
    uid: 9f56049c-fe5b-4e9d-b8f1-867e3590d393
  spec:
    sourcePod: network-check-source-685456655f-h9n7q
    targetEndpoint: a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:25:59Z"
      message: 'load-balancer-api-internal: tcp connection to a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.646434ms
      message: 'load-balancer-api-internal: tcp connection to a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:49:59Z"
    - latency: 9.537349ms
      message: 'load-balancer-api-internal: resolved host name a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:49:59Z"
    - latency: 4.275394ms
      message: 'load-balancer-api-internal: tcp connection to a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:48:59Z"
    - latency: 8.881049ms
      message: 'load-balancer-api-internal: resolved host name a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:48:59Z"
    - latency: 4.686757ms
      message: 'load-balancer-api-internal: tcp connection to a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:47:59Z"
    - latency: 8.940379ms
      message: 'load-balancer-api-internal: resolved host name a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:47:59Z"
    - latency: 5.457849ms
      message: 'load-balancer-api-internal: tcp connection to a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:46:59Z"
    - latency: 8.071756ms
      message: 'load-balancer-api-internal: resolved host name a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:46:59Z"
    - latency: 7.727614ms
      message: 'load-balancer-api-internal: tcp connection to a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:45:59Z"
    - latency: 10.084501ms
      message: 'load-balancer-api-internal: resolved host name a81f6809e16104c4294f4875501b5594-3e3009ffa03efd21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:45:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:19:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-211-to-network-check-target-ip-10-0-137-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-211.ec2.internal
      uid: 73dbd4c3-66f8-4245-83d1-b436157f1b39
    resourceVersion: "52705"
    uid: a4a6fffd-e4d4-45b9-99db-3e2bd909ae07
  spec:
    sourcePod: network-check-source-685456655f-h9n7q
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:26:59Z"
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.100808ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:47:59Z"
    - latency: 2.192494ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:46:59Z"
    - latency: 2.257832ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:45:59Z"
    - latency: 2.118595ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:44:59Z"
    - latency: 2.189793ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:43:59Z"
    - latency: 2.233138ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:42:59Z"
    - latency: 2.031233ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:41:59Z"
    - latency: 2.179203ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:40:59Z"
    - latency: 1.758362ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:39:59Z"
    - latency: 1.994886ms
      message: 'network-check-target-ip-10-0-137-9: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:38:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:19:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-211-to-network-check-target-ip-10-0-139-174
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-211.ec2.internal
      uid: 73dbd4c3-66f8-4245-83d1-b436157f1b39
    resourceVersion: "52706"
    uid: 7929dbb1-69d0-4e3b-8b4b-311bf07aaaff
  spec:
    sourcePod: network-check-source-685456655f-h9n7q
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:26:59Z"
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.338486ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:47:59Z"
    - latency: 2.127411ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:46:59Z"
    - latency: 2.515437ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:45:59Z"
    - latency: 2.225997ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:44:59Z"
    - latency: 2.643343ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:43:59Z"
    - latency: 2.235227ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:42:59Z"
    - latency: 1.877372ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:41:59Z"
    - latency: 2.173494ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:40:59Z"
    - latency: 2.079477ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:39:59Z"
    - latency: 1.824391ms
      message: 'network-check-target-ip-10-0-139-174: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:38:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:19:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-211-to-network-check-target-ip-10-0-143-211
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-211.ec2.internal
      uid: 73dbd4c3-66f8-4245-83d1-b436157f1b39
    resourceVersion: "52704"
    uid: 3c4508b6-8024-40f7-a736-f2d23ff18457
  spec:
    sourcePod: network-check-source-685456655f-h9n7q
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:26:59Z"
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.409323ms
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:47:59Z"
    - latency: 1.33269ms
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:46:59Z"
    - latency: 912.411µs
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:45:59Z"
    - latency: 916.268µs
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:44:59Z"
    - latency: 976.012µs
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:43:59Z"
    - latency: 1.08624ms
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:42:59Z"
    - latency: 922.97µs
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:41:59Z"
    - latency: 857.948µs
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:40:59Z"
    - latency: 1.271061ms
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:39:59Z"
    - latency: 1.050307ms
      message: 'network-check-target-ip-10-0-143-211: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:38:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T13:19:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-211-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-211.ec2.internal
      uid: 73dbd4c3-66f8-4245-83d1-b436157f1b39
    resourceVersion: "54176"
    uid: 15212f3f-26b3-44e9-b94c-f81fe508ef91
  spec:
    sourcePod: network-check-source-685456655f-h9n7q
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T13:25:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.73µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:49:59Z"
    - latency: 1.94678ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:49:59Z"
    - latency: 988.509µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:48:59Z"
    - latency: 1.944119ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:48:59Z"
    - latency: 1.207175ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:47:59Z"
    - latency: 2.074729ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:47:59Z"
    - latency: 1.064465ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:46:59Z"
    - latency: 1.854388ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:46:59Z"
    - latency: 773.126µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T13:45:59Z"
    - latency: 2.097534ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T13:45:59Z"
kind: List
metadata:
  resourceVersion: ""