apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:46:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-95-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-95.ec2.internal
      uid: 6c6cc470-d735-4869-89f4-142642814644
    resourceVersion: "46784"
    uid: 3b75d504-bdd7-4885-a19e-6c426ccd14d1
  spec:
    sourcePod: network-check-source-869dcfcdcd-rd8wm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:53:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.444875ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:14:46Z"
    - latency: 1.229357ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:13:46Z"
    - latency: 1.118623ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:12:46Z"
    - latency: 908.06µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:11:46Z"
    - latency: 1.068798ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:10:46Z"
    - latency: 994.971µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:09:46Z"
    - latency: 1.126975ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:08:46Z"
    - latency: 859.622µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:07:46Z"
    - latency: 1.144029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:06:46Z"
    - latency: 1.095123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:05:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:46:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-95-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-95.ec2.internal
      uid: 6c6cc470-d735-4869-89f4-142642814644
    resourceVersion: "48745"
    uid: eefc7e1e-f802-459c-9d78-e372b97c0373
  spec:
    sourcePod: network-check-source-869dcfcdcd-rd8wm
    targetEndpoint: a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:52:46Z"
      message: 'load-balancer-api-external: tcp connection to a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.614869ms
      message: 'load-balancer-api-external: tcp connection to a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:16:46Z"
    - latency: 6.492962ms
      message: 'load-balancer-api-external: resolved host name a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:16:46Z"
    - latency: 5.845686ms
      message: 'load-balancer-api-external: tcp connection to a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:15:46Z"
    - latency: 9.681998ms
      message: 'load-balancer-api-external: resolved host name a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:15:46Z"
    - latency: 3.590102ms
      message: 'load-balancer-api-external: tcp connection to a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:14:46Z"
    - latency: 6.959105ms
      message: 'load-balancer-api-external: resolved host name a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:14:46Z"
    - latency: 3.831604ms
      message: 'load-balancer-api-external: tcp connection to a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:13:46Z"
    - latency: 6.725292ms
      message: 'load-balancer-api-external: resolved host name a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:13:46Z"
    - latency: 4.752831ms
      message: 'load-balancer-api-external: tcp connection to a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:12:46Z"
    - latency: 6.551659ms
      message: 'load-balancer-api-external: resolved host name a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:12:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:46:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-95-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-95.ec2.internal
      uid: 6c6cc470-d735-4869-89f4-142642814644
    resourceVersion: "48746"
    uid: 1748ba48-de6f-4e34-b6e4-456bcfff6afa
  spec:
    sourcePod: network-check-source-869dcfcdcd-rd8wm
    targetEndpoint: a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:52:46Z"
      message: 'load-balancer-api-internal: tcp connection to a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.602731ms
      message: 'load-balancer-api-internal: tcp connection to a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:16:46Z"
    - latency: 6.571897ms
      message: 'load-balancer-api-internal: resolved host name a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:16:46Z"
    - latency: 6.111026ms
      message: 'load-balancer-api-internal: tcp connection to a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:15:46Z"
    - latency: 9.608395ms
      message: 'load-balancer-api-internal: resolved host name a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:15:46Z"
    - latency: 3.45564ms
      message: 'load-balancer-api-internal: tcp connection to a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:14:46Z"
    - latency: 7.052495ms
      message: 'load-balancer-api-internal: resolved host name a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:14:46Z"
    - latency: 3.838507ms
      message: 'load-balancer-api-internal: tcp connection to a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:13:46Z"
    - latency: 6.621737ms
      message: 'load-balancer-api-internal: resolved host name a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:13:46Z"
    - latency: 3.521298ms
      message: 'load-balancer-api-internal: tcp connection to a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:12:46Z"
    - latency: 6.605604ms
      message: 'load-balancer-api-internal: resolved host name a4266547a6a1a430088bec3d236533c8-22d0dc2d20fcd382.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:12:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:46:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-95-to-network-check-target-ip-10-0-135-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-95.ec2.internal
      uid: 6c6cc470-d735-4869-89f4-142642814644
    resourceVersion: "46782"
    uid: 0dfff1ee-22b0-4cdb-a8ae-2630eae283bc
  spec:
    sourcePod: network-check-source-869dcfcdcd-rd8wm
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:53:46Z"
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.162896ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:14:46Z"
    - latency: 2.318074ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:13:46Z"
    - latency: 2.436183ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:12:46Z"
    - latency: 2.632713ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:11:46Z"
    - latency: 2.324418ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:10:46Z"
    - latency: 2.701205ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:09:46Z"
    - latency: 2.106727ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:08:46Z"
    - latency: 2.403974ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:07:46Z"
    - latency: 2.596244ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:06:46Z"
    - latency: 2.095608ms
      message: 'network-check-target-ip-10-0-135-41: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:05:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:46:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-95-to-network-check-target-ip-10-0-140-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-95.ec2.internal
      uid: 6c6cc470-d735-4869-89f4-142642814644
    resourceVersion: "46781"
    uid: 8307573b-dc75-4872-935c-984257f5f1ca
  spec:
    sourcePod: network-check-source-869dcfcdcd-rd8wm
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:53:46Z"
      message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.647118ms
      message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:14:46Z"
    - latency: 830.012µs
      message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:13:46Z"
    - latency: 1.098082ms
      message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:12:46Z"
    - latency: 1.10384ms
      message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:11:46Z"
    - latency: 1.176723ms
      message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:10:46Z"
    - latency: 1.373884ms
      message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:09:46Z"
    - latency: 872.263µs
      message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:08:46Z"
    - latency: 1.26748ms
      message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:07:46Z"
    - latency: 755.66µs
      message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:06:46Z"
    - latency: 834.391µs
      message: 'network-check-target-ip-10-0-140-95: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:05:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:46:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-95-to-network-check-target-ip-10-0-142-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-95.ec2.internal
      uid: 6c6cc470-d735-4869-89f4-142642814644
    resourceVersion: "46783"
    uid: 6d480fe1-5815-4761-ad25-a50f9f38d755
  spec:
    sourcePod: network-check-source-869dcfcdcd-rd8wm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:53:46Z"
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.43218ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:14:46Z"
    - latency: 2.282505ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:13:46Z"
    - latency: 2.361181ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:12:46Z"
    - latency: 2.351447ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:11:46Z"
    - latency: 2.637903ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:10:46Z"
    - latency: 2.3757ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:09:46Z"
    - latency: 2.207711ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:08:46Z"
    - latency: 1.919388ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:07:46Z"
    - latency: 2.119521ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:06:46Z"
    - latency: 2.40692ms
      message: 'network-check-target-ip-10-0-142-236: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:05:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T14:46:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-95-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-95.ec2.internal
      uid: 6c6cc470-d735-4869-89f4-142642814644
    resourceVersion: "48744"
    uid: cc3c9029-24bd-4276-84e5-0c87579ae140
  spec:
    sourcePod: network-check-source-869dcfcdcd-rd8wm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T14:52:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 902.943µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:16:46Z"
    - latency: 1.827129ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:16:46Z"
    - latency: 924.507µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:15:46Z"
    - latency: 1.713029ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:15:46Z"
    - latency: 871.82µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:14:46Z"
    - latency: 1.7625ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:14:46Z"
    - latency: 1.223256ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:13:46Z"
    - latency: 1.776499ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:13:46Z"
    - latency: 1.118571ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T15:12:46Z"
    - latency: 1.893204ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T15:12:46Z"
kind: List
metadata:
  resourceVersion: ""