apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T23:04:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-78-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-78.ec2.internal
      uid: c2a89585-25ce-4ad3-9b78-ca8cd444d898
    resourceVersion: "44622"
    uid: 6fae79a0-356b-45de-aa07-b413367966d8
  spec:
    sourcePod: network-check-source-dbd9cf844-6vdc4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T23:11:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 928.399µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:32:48Z"
    - latency: 1.697531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:31:48Z"
    - latency: 1.016914ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:30:48Z"
    - latency: 1.328438ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:29:48Z"
    - latency: 949.07µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:28:48Z"
    - latency: 879.35µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:27:48Z"
    - latency: 1.132971ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:26:48Z"
    - latency: 1.130536ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:25:48Z"
    - latency: 1.105088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:24:48Z"
    - latency: 1.260656ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:23:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T23:04:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-78-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-78.ec2.internal
      uid: c2a89585-25ce-4ad3-9b78-ca8cd444d898
    resourceVersion: "46706"
    uid: 27c452a3-55df-4d2e-b28a-761099cfa7cb
  spec:
    sourcePod: network-check-source-dbd9cf844-6vdc4
    targetEndpoint: a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T23:10:48Z"
      message: 'load-balancer-api-external: tcp connection to a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.31964ms
      message: 'load-balancer-api-external: tcp connection to a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:34:48Z"
    - latency: 8.64638ms
      message: 'load-balancer-api-external: resolved host name a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:34:48Z"
    - latency: 4.637122ms
      message: 'load-balancer-api-external: tcp connection to a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:33:48Z"
    - latency: 8.584301ms
      message: 'load-balancer-api-external: resolved host name a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:33:48Z"
    - latency: 3.420154ms
      message: 'load-balancer-api-external: tcp connection to a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:32:48Z"
    - latency: 8.753864ms
      message: 'load-balancer-api-external: resolved host name a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:32:48Z"
    - latency: 4.084709ms
      message: 'load-balancer-api-external: tcp connection to a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:31:48Z"
    - latency: 9.900724ms
      message: 'load-balancer-api-external: resolved host name a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:31:48Z"
    - latency: 3.334942ms
      message: 'load-balancer-api-external: tcp connection to a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:30:48Z"
    - latency: 9.022724ms
      message: 'load-balancer-api-external: resolved host name a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:30:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T23:04:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-78-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-78.ec2.internal
      uid: c2a89585-25ce-4ad3-9b78-ca8cd444d898
    resourceVersion: "46705"
    uid: a3a9e890-ced2-4cca-aa08-d07fbfa31155
  spec:
    sourcePod: network-check-source-dbd9cf844-6vdc4
    targetEndpoint: a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T23:10:48Z"
      message: 'load-balancer-api-internal: tcp connection to a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.998289ms
      message: 'load-balancer-api-internal: tcp connection to a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:34:48Z"
    - latency: 8.58442ms
      message: 'load-balancer-api-internal: resolved host name a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:34:48Z"
    - latency: 4.654768ms
      message: 'load-balancer-api-internal: tcp connection to a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:33:48Z"
    - latency: 8.490252ms
      message: 'load-balancer-api-internal: resolved host name a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:33:48Z"
    - latency: 3.419407ms
      message: 'load-balancer-api-internal: tcp connection to a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:32:48Z"
    - latency: 8.700227ms
      message: 'load-balancer-api-internal: resolved host name a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:32:48Z"
    - latency: 4.06688ms
      message: 'load-balancer-api-internal: tcp connection to a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:31:48Z"
    - latency: 9.9454ms
      message: 'load-balancer-api-internal: resolved host name a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:31:48Z"
    - latency: 5.05587ms
      message: 'load-balancer-api-internal: tcp connection to a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:30:48Z"
    - latency: 8.995946ms
      message: 'load-balancer-api-internal: resolved host name a8e3a5ff2cbc942daaf91aec201ab51c-d7f91457bc83ea70.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:30:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T23:04:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-78-to-network-check-target-ip-10-0-129-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-78.ec2.internal
      uid: c2a89585-25ce-4ad3-9b78-ca8cd444d898
    resourceVersion: "44621"
    uid: eafb0918-9ccc-4c7f-881e-3b71eab4a185
  spec:
    sourcePod: network-check-source-dbd9cf844-6vdc4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T23:11:48Z"
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.450892ms
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:32:48Z"
    - latency: 2.296542ms
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:31:48Z"
    - latency: 2.25103ms
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:30:48Z"
    - latency: 2.265203ms
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:29:48Z"
    - latency: 2.264272ms
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:28:48Z"
    - latency: 2.327824ms
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:27:48Z"
    - latency: 2.495709ms
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:26:48Z"
    - latency: 2.187695ms
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:25:48Z"
    - latency: 2.549283ms
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:24:48Z"
    - latency: 2.243205ms
      message: 'network-check-target-ip-10-0-129-238: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:23:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T23:04:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-78-to-network-check-target-ip-10-0-136-78
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-78.ec2.internal
      uid: c2a89585-25ce-4ad3-9b78-ca8cd444d898
    resourceVersion: "44619"
    uid: 045b99d3-4744-4a97-a51a-1e169a40f54a
  spec:
    sourcePod: network-check-source-dbd9cf844-6vdc4
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T23:11:48Z"
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 870.755µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:32:48Z"
    - latency: 936.45µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:31:48Z"
    - latency: 918.582µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:30:48Z"
    - latency: 930.256µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:29:48Z"
    - latency: 837.965µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:28:48Z"
    - latency: 920.288µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:27:48Z"
    - latency: 837.604µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:26:48Z"
    - latency: 932.227µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:25:48Z"
    - latency: 882.762µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:24:48Z"
    - latency: 899.328µs
      message: 'network-check-target-ip-10-0-136-78: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:23:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T23:04:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-78-to-network-check-target-ip-10-0-139-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-78.ec2.internal
      uid: c2a89585-25ce-4ad3-9b78-ca8cd444d898
    resourceVersion: "44620"
    uid: 5fb2a222-5063-4bac-b0c5-a24c1429ec47
  spec:
    sourcePod: network-check-source-dbd9cf844-6vdc4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T23:11:48Z"
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.402101ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:32:48Z"
    - latency: 2.26498ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:31:48Z"
    - latency: 1.954107ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:30:48Z"
    - latency: 2.303012ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:29:48Z"
    - latency: 2.358306ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:28:48Z"
    - latency: 2.339134ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:27:48Z"
    - latency: 2.115519ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:26:48Z"
    - latency: 2.247618ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:25:48Z"
    - latency: 2.182156ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:24:48Z"
    - latency: 2.337937ms
      message: 'network-check-target-ip-10-0-139-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:23:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T23:04:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-78-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-78.ec2.internal
      uid: c2a89585-25ce-4ad3-9b78-ca8cd444d898
    resourceVersion: "46704"
    uid: f09ad6df-9c3a-4f0f-b31c-1233381a698e
  spec:
    sourcePod: network-check-source-dbd9cf844-6vdc4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T23:10:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 816.108µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:34:48Z"
    - latency: 1.816177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:34:48Z"
    - latency: 905.722µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:33:48Z"
    - latency: 1.624253ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:33:48Z"
    - latency: 907.742µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:32:48Z"
    - latency: 1.842264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:32:48Z"
    - latency: 936.693µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:31:48Z"
    - latency: 2.282489ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:31:48Z"
    - latency: 899.144µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T23:30:48Z"
    - latency: 1.69828ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T23:30:48Z"
kind: List
metadata:
  resourceVersion: ""