apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T20:40:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-185-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-185.ec2.internal
      uid: 42f37179-afed-4f5b-ac99-e7b7332d05b9
    resourceVersion: "58767"
    uid: 1643b5d1-d170-460e-9144-212ba861558b
  spec:
    sourcePod: network-check-source-6f8b768455-nn88n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T20:47:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.032712ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:15:53Z"
    - latency: 917.398µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:14:53Z"
    - latency: 1.05138ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:13:53Z"
    - latency: 1.31909ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:12:53Z"
    - latency: 1.694123ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:11:53Z"
    - latency: 1.502563ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:10:53Z"
    - latency: 1.700132ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:09:53Z"
    - latency: 1.004569ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:08:53Z"
    - latency: 1.060472ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:07:53Z"
    - latency: 1.00248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:06:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T20:40:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-185-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-185.ec2.internal
      uid: 42f37179-afed-4f5b-ac99-e7b7332d05b9
    resourceVersion: "54410"
    uid: b1d1d979-e892-408f-a790-cdb886f624c8
  spec:
    sourcePod: network-check-source-6f8b768455-nn88n
    targetEndpoint: a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T20:46:53Z"
      message: 'load-balancer-api-external: tcp connection to a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.965364ms
      message: 'load-balancer-api-external: tcp connection to a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:10:53Z"
    - latency: 10.02723ms
      message: 'load-balancer-api-external: resolved host name a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:10:53Z"
    - latency: 4.244316ms
      message: 'load-balancer-api-external: tcp connection to a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:09:53Z"
    - latency: 7.206761ms
      message: 'load-balancer-api-external: resolved host name a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:09:53Z"
    - latency: 5.816157ms
      message: 'load-balancer-api-external: tcp connection to a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:08:53Z"
    - latency: 6.794985ms
      message: 'load-balancer-api-external: resolved host name a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:08:53Z"
    - latency: 5.651714ms
      message: 'load-balancer-api-external: tcp connection to a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:07:53Z"
    - latency: 6.976788ms
      message: 'load-balancer-api-external: resolved host name a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:07:53Z"
    - latency: 5.485997ms
      message: 'load-balancer-api-external: tcp connection to a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:06:53Z"
    - latency: 7.230494ms
      message: 'load-balancer-api-external: resolved host name a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:06:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T20:40:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-185-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-185.ec2.internal
      uid: 42f37179-afed-4f5b-ac99-e7b7332d05b9
    resourceVersion: "54411"
    uid: 1576e510-82af-4f7f-aef2-b019b55f5170
  spec:
    sourcePod: network-check-source-6f8b768455-nn88n
    targetEndpoint: a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T20:46:53Z"
      message: 'load-balancer-api-internal: tcp connection to a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.523218ms
      message: 'load-balancer-api-internal: tcp connection to a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:10:53Z"
    - latency: 10.110907ms
      message: 'load-balancer-api-internal: resolved host name a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:10:53Z"
    - latency: 5.764087ms
      message: 'load-balancer-api-internal: tcp connection to a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:09:53Z"
    - latency: 7.40149ms
      message: 'load-balancer-api-internal: resolved host name a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:09:53Z"
    - latency: 5.798147ms
      message: 'load-balancer-api-internal: tcp connection to a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:08:53Z"
    - latency: 6.80124ms
      message: 'load-balancer-api-internal: resolved host name a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:08:53Z"
    - latency: 5.619611ms
      message: 'load-balancer-api-internal: tcp connection to a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:07:53Z"
    - latency: 6.909144ms
      message: 'load-balancer-api-internal: resolved host name a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:07:53Z"
    - latency: 5.122215ms
      message: 'load-balancer-api-internal: tcp connection to a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:06:53Z"
    - latency: 7.251327ms
      message: 'load-balancer-api-internal: resolved host name a20becb481bc6450790cc89788eb0089-d2d4c0d3de25c902.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:06:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T20:40:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-185-to-network-check-target-ip-10-0-129-103
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-185.ec2.internal
      uid: 42f37179-afed-4f5b-ac99-e7b7332d05b9
    resourceVersion: "58765"
    uid: b7588a75-9ee1-4c7f-a9c4-5d8140f938c7
  spec:
    sourcePod: network-check-source-6f8b768455-nn88n
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T20:47:53Z"
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.470026ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:15:53Z"
    - latency: 2.482123ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:14:53Z"
    - latency: 2.120797ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:13:53Z"
    - latency: 2.375623ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:12:53Z"
    - latency: 2.877066ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:11:53Z"
    - latency: 2.412289ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:10:53Z"
    - latency: 2.225198ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:09:53Z"
    - latency: 2.457885ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:08:53Z"
    - latency: 2.589512ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:07:53Z"
    - latency: 2.167896ms
      message: 'network-check-target-ip-10-0-129-103: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:06:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T20:40:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-185-to-network-check-target-ip-10-0-141-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-185.ec2.internal
      uid: 42f37179-afed-4f5b-ac99-e7b7332d05b9
    resourceVersion: "58764"
    uid: 6d6e5405-b2ff-414e-82d3-bda3d3a6d27f
  spec:
    sourcePod: network-check-source-6f8b768455-nn88n
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T20:47:53Z"
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 928.301µs
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:15:53Z"
    - latency: 993.772µs
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:14:53Z"
    - latency: 1.068618ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:13:53Z"
    - latency: 1.696043ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:12:53Z"
    - latency: 1.617881ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:11:53Z"
    - latency: 1.546912ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:10:53Z"
    - latency: 967.971µs
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:09:53Z"
    - latency: 1.127361ms
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:08:53Z"
    - latency: 992.535µs
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:07:53Z"
    - latency: 787.866µs
      message: 'network-check-target-ip-10-0-141-185: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:06:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T20:40:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-185-to-network-check-target-ip-10-0-143-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-185.ec2.internal
      uid: 42f37179-afed-4f5b-ac99-e7b7332d05b9
    resourceVersion: "58766"
    uid: e3bb5650-55a2-478c-8e19-a684cb86af05
  spec:
    sourcePod: network-check-source-6f8b768455-nn88n
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T20:47:53Z"
      message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.827847ms
      message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:15:53Z"
    - latency: 2.109474ms
      message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:14:53Z"
    - latency: 1.794587ms
      message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:13:53Z"
    - latency: 2.063695ms
      message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:12:53Z"
    - latency: 2.119514ms
      message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:11:53Z"
    - latency: 2.446903ms
      message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:10:53Z"
    - latency: 1.961524ms
      message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:09:53Z"
    - latency: 2.366546ms
      message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:08:53Z"
    - latency: 2.186355ms
      message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:07:53Z"
    - latency: 2.369712ms
      message: 'network-check-target-ip-10-0-143-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:06:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-10T20:40:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-141-185-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-141-185.ec2.internal
      uid: 42f37179-afed-4f5b-ac99-e7b7332d05b9
    resourceVersion: "54409"
    uid: 466a43e7-b13c-4651-8b28-0681ebcc58dd
  spec:
    sourcePod: network-check-source-6f8b768455-nn88n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-10T20:46:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.091724ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:10:53Z"
    - latency: 2.418935ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:10:53Z"
    - latency: 785.222µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:09:53Z"
    - latency: 2.054144ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:09:53Z"
    - latency: 1.052081ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:08:53Z"
    - latency: 1.651822ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:08:53Z"
    - latency: 1.397722ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:07:53Z"
    - latency: 1.716769ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:07:53Z"
    - latency: 891.341µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-10T21:06:53Z"
    - latency: 2.361556ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-10T21:06:53Z"
kind: List
metadata:
  resourceVersion: ""