apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T03:11:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-52-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-52.ec2.internal
      uid: 449cc147-0bb5-4054-a281-1a0d1a606c76
    resourceVersion: "54381"
    uid: ab2cd3cb-080f-492f-907b-fa51877625ec
  spec:
    sourcePod: network-check-source-685456655f-hrtwd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T03:18:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.247812ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:39:47Z"
    - latency: 1.187352ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:38:47Z"
    - latency: 1.286706ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:37:47Z"
    - latency: 852.07µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:36:47Z"
    - latency: 887.052µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:35:47Z"
    - latency: 1.261085ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:34:47Z"
    - latency: 1.160791ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:33:47Z"
    - latency: 874.465µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:32:47Z"
    - latency: 1.156484ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:31:47Z"
    - latency: 1.189227ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:30:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T03:11:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-52-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-52.ec2.internal
      uid: 449cc147-0bb5-4054-a281-1a0d1a606c76
    resourceVersion: "56001"
    uid: 7c90646b-ecd5-4212-b88e-f1373ea08b58
  spec:
    sourcePod: network-check-source-685456655f-hrtwd
    targetEndpoint: afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T03:17:47Z"
      message: 'load-balancer-api-external: tcp connection to afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.251582ms
      message: 'load-balancer-api-external: tcp connection to afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:41:47Z"
    - latency: 12.659988ms
      message: 'load-balancer-api-external: resolved host name afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:41:47Z"
    - latency: 4.753081ms
      message: 'load-balancer-api-external: tcp connection to afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:40:47Z"
    - latency: 7.807764ms
      message: 'load-balancer-api-external: resolved host name afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:40:47Z"
    - latency: 3.345853ms
      message: 'load-balancer-api-external: tcp connection to afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:39:47Z"
    - latency: 9.319632ms
      message: 'load-balancer-api-external: resolved host name afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:39:47Z"
    - latency: 4.836432ms
      message: 'load-balancer-api-external: tcp connection to afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:38:47Z"
    - latency: 8.15226ms
      message: 'load-balancer-api-external: resolved host name afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:38:47Z"
    - latency: 3.428747ms
      message: 'load-balancer-api-external: tcp connection to afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:37:47Z"
    - latency: 9.257498ms
      message: 'load-balancer-api-external: resolved host name afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:37:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T03:11:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-52-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-52.ec2.internal
      uid: 449cc147-0bb5-4054-a281-1a0d1a606c76
    resourceVersion: "56002"
    uid: 56420e78-88f7-44ad-81eb-f7025dff361f
  spec:
    sourcePod: network-check-source-685456655f-hrtwd
    targetEndpoint: afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T03:17:47Z"
      message: 'load-balancer-api-internal: tcp connection to afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.330631ms
      message: 'load-balancer-api-internal: tcp connection to afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:41:47Z"
    - latency: 12.591934ms
      message: 'load-balancer-api-internal: resolved host name afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:41:47Z"
    - latency: 3.250571ms
      message: 'load-balancer-api-internal: tcp connection to afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:40:47Z"
    - latency: 7.759969ms
      message: 'load-balancer-api-internal: resolved host name afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:40:47Z"
    - latency: 4.623107ms
      message: 'load-balancer-api-internal: tcp connection to afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:39:47Z"
    - latency: 9.339827ms
      message: 'load-balancer-api-internal: resolved host name afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:39:47Z"
    - latency: 4.850305ms
      message: 'load-balancer-api-internal: tcp connection to afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:38:47Z"
    - latency: 8.192138ms
      message: 'load-balancer-api-internal: resolved host name afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:38:47Z"
    - latency: 3.545148ms
      message: 'load-balancer-api-internal: tcp connection to afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:37:47Z"
    - latency: 9.344654ms
      message: 'load-balancer-api-internal: resolved host name afd4c48dcba794775a67b8ed2e913204-49889b370cf33bd4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:37:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T03:11:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-52-to-network-check-target-ip-10-0-138-152
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-52.ec2.internal
      uid: 449cc147-0bb5-4054-a281-1a0d1a606c76
    resourceVersion: "54379"
    uid: ee5a135b-5f83-4de4-a5e0-44d9f8108016
  spec:
    sourcePod: network-check-source-685456655f-hrtwd
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T03:18:47Z"
      message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.214741ms
      message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:39:47Z"
    - latency: 2.048947ms
      message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:38:47Z"
    - latency: 2.120167ms
      message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:37:47Z"
    - latency: 1.982493ms
      message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:36:47Z"
    - latency: 2.016399ms
      message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:35:47Z"
    - latency: 1.860294ms
      message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:34:47Z"
    - latency: 2.013017ms
      message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:33:47Z"
    - latency: 2.22585ms
      message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:32:47Z"
    - latency: 2.055904ms
      message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:31:47Z"
    - latency: 2.125025ms
      message: 'network-check-target-ip-10-0-138-152: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:30:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T03:11:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-52-to-network-check-target-ip-10-0-143-233
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-52.ec2.internal
      uid: 449cc147-0bb5-4054-a281-1a0d1a606c76
    resourceVersion: "54380"
    uid: 2bcb2f77-e136-4eb5-a64e-5d322e5e561c
  spec:
    sourcePod: network-check-source-685456655f-hrtwd
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T03:18:47Z"
      message: 'network-check-target-ip-10-0-143-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.344621ms
      message: 'network-check-target-ip-10-0-143-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:39:47Z"
    - latency: 2.466333ms
      message: 'network-check-target-ip-10-0-143-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:38:47Z"
    - latency: 2.343987ms
      message: 'network-check-target-ip-10-0-143-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:37:47Z"
    - latency: 2.308521ms
      message: 'network-check-target-ip-10-0-143-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:36:47Z"
    - latency: 2.403322ms
      message: 'network-check-target-ip-10-0-143-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:35:47Z"
    - latency: 2.259134ms
      message: 'network-check-target-ip-10-0-143-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:34:47Z"
    - latency: 2.367162ms
      message: 'network-check-target-ip-10-0-143-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:33:47Z"
    - latency: 2.499428ms
      message: 'network-check-target-ip-10-0-143-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:32:47Z"
    - latency: 2.63129ms
      message: 'network-check-target-ip-10-0-143-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:31:47Z"
    - latency: 2.206122ms
      message: 'network-check-target-ip-10-0-143-233: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:30:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T03:11:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-52-to-network-check-target-ip-10-0-143-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-52.ec2.internal
      uid: 449cc147-0bb5-4054-a281-1a0d1a606c76
    resourceVersion: "54378"
    uid: ac8ae350-b8ff-4902-9640-e5314a17b649
  spec:
    sourcePod: network-check-source-685456655f-hrtwd
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T03:18:47Z"
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.269303ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:39:47Z"
    - latency: 980.58µs
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:38:47Z"
    - latency: 1.396169ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:37:47Z"
    - latency: 878.589µs
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:36:47Z"
    - latency: 960.148µs
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:35:47Z"
    - latency: 997.018µs
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:34:47Z"
    - latency: 966.238µs
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:33:47Z"
    - latency: 1.184873ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:32:47Z"
    - latency: 1.300815ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:31:47Z"
    - latency: 1.142693ms
      message: 'network-check-target-ip-10-0-143-52: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:30:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-09T03:11:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-52-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-52.ec2.internal
      uid: 449cc147-0bb5-4054-a281-1a0d1a606c76
    resourceVersion: "56000"
    uid: d8bb118a-ca19-4ddc-84e3-b98536a02367
  spec:
    sourcePod: network-check-source-685456655f-hrtwd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-09T03:17:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 889.887µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:41:47Z"
    - latency: 1.554456ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:41:47Z"
    - latency: 970.497µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:40:47Z"
    - latency: 1.851745ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:40:47Z"
    - latency: 767.719µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:39:47Z"
    - latency: 2.137542ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:39:47Z"
    - latency: 853.014µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:38:47Z"
    - latency: 1.766377ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:38:47Z"
    - latency: 845.511µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-09T03:37:47Z"
    - latency: 2.071706ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-09T03:37:47Z"
kind: List
metadata:
  resourceVersion: ""