apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:40:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-61.ec2.internal
      uid: 72bbd437-fde9-4e3b-b8b5-897c2bd01c97
    resourceVersion: "38538"
    uid: 9dcc3602-e22c-4265-b5fd-9f409d80af3d
  spec:
    sourcePod: network-check-source-7cbc45fddc-9rxdd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:47:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.042198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:29:48Z"
    - latency: 859.05µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:28:48Z"
    - latency: 1.346692ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:27:48Z"
    - latency: 1.42824ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:26:48Z"
    - latency: 920.818µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:25:48Z"
    - latency: 1.054184ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:24:48Z"
    - latency: 1.024172ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:23:48Z"
    - latency: 1.013735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:22:48Z"
    - latency: 1.17111ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:21:48Z"
    - latency: 1.038198ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:20:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:40:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-61.ec2.internal
      uid: 72bbd437-fde9-4e3b-b8b5-897c2bd01c97
    resourceVersion: "38117"
    uid: 143a628e-052b-4b05-884d-103f2d8cb06a
  spec:
    sourcePod: network-check-source-7cbc45fddc-9rxdd
    targetEndpoint: a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:46:49Z"
      message: 'load-balancer-api-external: tcp connection to a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.911698ms
      message: 'load-balancer-api-external: tcp connection to a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:28:48Z"
    - latency: 6.130446ms
      message: 'load-balancer-api-external: resolved host name a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:28:48Z"
    - latency: 5.265708ms
      message: 'load-balancer-api-external: tcp connection to a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:27:48Z"
    - latency: 7.629808ms
      message: 'load-balancer-api-external: resolved host name a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:27:48Z"
    - latency: 4.859307ms
      message: 'load-balancer-api-external: tcp connection to a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:26:48Z"
    - latency: 6.70151ms
      message: 'load-balancer-api-external: resolved host name a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:26:48Z"
    - latency: 6.32102ms
      message: 'load-balancer-api-external: tcp connection to a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:25:48Z"
    - latency: 6.645244ms
      message: 'load-balancer-api-external: resolved host name a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:25:48Z"
    - latency: 3.958195ms
      message: 'load-balancer-api-external: tcp connection to a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:24:48Z"
    - latency: 6.581205ms
      message: 'load-balancer-api-external: resolved host name a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:24:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:40:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-61.ec2.internal
      uid: 72bbd437-fde9-4e3b-b8b5-897c2bd01c97
    resourceVersion: "38118"
    uid: 29d9a174-64af-4f5a-a806-5718686fb615
  spec:
    sourcePod: network-check-source-7cbc45fddc-9rxdd
    targetEndpoint: a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:46:49Z"
      message: 'load-balancer-api-internal: tcp connection to a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.90009ms
      message: 'load-balancer-api-internal: tcp connection to a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:28:48Z"
    - latency: 6.359727ms
      message: 'load-balancer-api-internal: resolved host name a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:28:48Z"
    - latency: 5.219497ms
      message: 'load-balancer-api-internal: tcp connection to a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:27:48Z"
    - latency: 7.667844ms
      message: 'load-balancer-api-internal: resolved host name a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:27:48Z"
    - latency: 4.755329ms
      message: 'load-balancer-api-internal: tcp connection to a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:26:48Z"
    - latency: 6.720006ms
      message: 'load-balancer-api-internal: resolved host name a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:26:48Z"
    - latency: 6.352906ms
      message: 'load-balancer-api-internal: tcp connection to a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:25:48Z"
    - latency: 6.575081ms
      message: 'load-balancer-api-internal: resolved host name a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:25:48Z"
    - latency: 4.338092ms
      message: 'load-balancer-api-internal: tcp connection to a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:24:48Z"
    - latency: 6.635127ms
      message: 'load-balancer-api-internal: resolved host name a53a7ad50fef7478eaba743342f0d1b3-94cb3a4bdf0471de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:24:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:40:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-61-to-network-check-target-ip-10-0-136-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-61.ec2.internal
      uid: 72bbd437-fde9-4e3b-b8b5-897c2bd01c97
    resourceVersion: "38537"
    uid: 5673cb55-d7e3-488d-9f45-fea14e211d6c
  spec:
    sourcePod: network-check-source-7cbc45fddc-9rxdd
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:47:48Z"
      message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.875239ms
      message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:29:48Z"
    - latency: 2.067111ms
      message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:28:48Z"
    - latency: 2.044506ms
      message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:27:48Z"
    - latency: 1.921028ms
      message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:26:48Z"
    - latency: 1.690162ms
      message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:25:48Z"
    - latency: 1.873626ms
      message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:24:48Z"
    - latency: 1.920198ms
      message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:23:48Z"
    - latency: 2.173853ms
      message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:22:48Z"
    - latency: 1.894606ms
      message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:21:48Z"
    - latency: 1.698847ms
      message: 'network-check-target-ip-10-0-136-207: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:20:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:40:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-61-to-network-check-target-ip-10-0-137-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-61.ec2.internal
      uid: 72bbd437-fde9-4e3b-b8b5-897c2bd01c97
    resourceVersion: "38535"
    uid: 98a65d58-1413-46ad-82ca-f583f7921aab
  spec:
    sourcePod: network-check-source-7cbc45fddc-9rxdd
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:47:48Z"
      message: 'network-check-target-ip-10-0-137-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 986.422µs
      message: 'network-check-target-ip-10-0-137-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:29:48Z"
    - latency: 1.097159ms
      message: 'network-check-target-ip-10-0-137-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:28:48Z"
    - latency: 1.380943ms
      message: 'network-check-target-ip-10-0-137-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:27:48Z"
    - latency: 1.374985ms
      message: 'network-check-target-ip-10-0-137-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:26:48Z"
    - latency: 860.947µs
      message: 'network-check-target-ip-10-0-137-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:25:48Z"
    - latency: 1.033826ms
      message: 'network-check-target-ip-10-0-137-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:24:48Z"
    - latency: 996.545µs
      message: 'network-check-target-ip-10-0-137-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:23:48Z"
    - latency: 965.316µs
      message: 'network-check-target-ip-10-0-137-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:22:48Z"
    - latency: 919.535µs
      message: 'network-check-target-ip-10-0-137-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:21:48Z"
    - latency: 1.003607ms
      message: 'network-check-target-ip-10-0-137-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:20:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:40:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-61-to-network-check-target-ip-10-0-142-19
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-61.ec2.internal
      uid: 72bbd437-fde9-4e3b-b8b5-897c2bd01c97
    resourceVersion: "38536"
    uid: a8a8d699-bb1b-4b0f-94b7-d8ce9e6d9c7d
  spec:
    sourcePod: network-check-source-7cbc45fddc-9rxdd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:47:48Z"
      message: 'network-check-target-ip-10-0-142-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.409683ms
      message: 'network-check-target-ip-10-0-142-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:29:48Z"
    - latency: 2.404648ms
      message: 'network-check-target-ip-10-0-142-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:28:48Z"
    - latency: 2.475087ms
      message: 'network-check-target-ip-10-0-142-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:27:48Z"
    - latency: 2.403215ms
      message: 'network-check-target-ip-10-0-142-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:26:48Z"
    - latency: 2.24519ms
      message: 'network-check-target-ip-10-0-142-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:25:48Z"
    - latency: 2.420694ms
      message: 'network-check-target-ip-10-0-142-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:24:48Z"
    - latency: 2.431817ms
      message: 'network-check-target-ip-10-0-142-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:23:48Z"
    - latency: 2.544409ms
      message: 'network-check-target-ip-10-0-142-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:22:48Z"
    - latency: 2.429742ms
      message: 'network-check-target-ip-10-0-142-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:21:48Z"
    - latency: 2.270322ms
      message: 'network-check-target-ip-10-0-142-19: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:20:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T19:40:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-61.ec2.internal
      uid: 72bbd437-fde9-4e3b-b8b5-897c2bd01c97
    resourceVersion: "38116"
    uid: b64996ee-41f5-4046-bb58-df4bdfe3752c
  spec:
    sourcePod: network-check-source-7cbc45fddc-9rxdd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T19:46:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.457µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:28:48Z"
    - latency: 1.666021ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:28:48Z"
    - latency: 1.007909ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:27:48Z"
    - latency: 2.311803ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:27:48Z"
    - latency: 903.886µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:26:48Z"
    - latency: 1.784477ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:26:48Z"
    - latency: 1.106659ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:25:48Z"
    - latency: 1.624295ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:25:48Z"
    - latency: 1.137331ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T20:24:48Z"
    - latency: 1.816005ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T20:24:48Z"
kind: List
metadata:
  resourceVersion: ""