apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:06:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-102-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-102.ec2.internal
      uid: 4cbb28dd-4b1b-47b9-9314-e4c6021ed6dd
    resourceVersion: "113064"
    uid: 1ac2d74b-cd08-4c27-b05d-d0408e4bb834
  spec:
    sourcePod: network-check-source-6f78d59f99-59msh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:13:08Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.028523ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:55:08Z"
    - latency: 1.221238ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:54:08Z"
    - latency: 1.334482ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:53:08Z"
    - latency: 887.962µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:52:08Z"
    - latency: 1.356564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:51:08Z"
    - latency: 978.325µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:50:08Z"
    - latency: 1.233688ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:49:08Z"
    - latency: 1.246279ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:48:08Z"
    - latency: 1.078514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:47:08Z"
    - latency: 2.033779ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:46:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:06:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-102-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-102.ec2.internal
      uid: 4cbb28dd-4b1b-47b9-9314-e4c6021ed6dd
    resourceVersion: "112172"
    uid: c328a181-3fb8-4c1a-bdf4-278e70bcbc24
  spec:
    sourcePod: network-check-source-6f78d59f99-59msh
    targetEndpoint: a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:12:08Z"
      message: 'load-balancer-api-external: tcp connection to a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.568926ms
      message: 'load-balancer-api-external: tcp connection to a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:54:08Z"
    - latency: 7.590727ms
      message: 'load-balancer-api-external: resolved host name a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:54:08Z"
    - latency: 18.068848ms
      message: 'load-balancer-api-external: tcp connection to a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:53:08Z"
    - latency: 6.758237ms
      message: 'load-balancer-api-external: resolved host name a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:53:08Z"
    - latency: 17.344586ms
      message: 'load-balancer-api-external: tcp connection to a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:52:08Z"
    - latency: 12.224831ms
      message: 'load-balancer-api-external: resolved host name a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:52:08Z"
    - latency: 16.455026ms
      message: 'load-balancer-api-external: tcp connection to a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:51:08Z"
    - latency: 7.78805ms
      message: 'load-balancer-api-external: resolved host name a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:51:08Z"
    - latency: 16.856576ms
      message: 'load-balancer-api-external: tcp connection to a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:50:08Z"
    - latency: 7.695636ms
      message: 'load-balancer-api-external: resolved host name a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:50:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:06:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-102-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-102.ec2.internal
      uid: 4cbb28dd-4b1b-47b9-9314-e4c6021ed6dd
    resourceVersion: "112173"
    uid: c33e720d-3ab1-4b7e-a953-5a320884869a
  spec:
    sourcePod: network-check-source-6f78d59f99-59msh
    targetEndpoint: a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:12:08Z"
      message: 'load-balancer-api-internal: tcp connection to a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.61784ms
      message: 'load-balancer-api-internal: tcp connection to a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:54:08Z"
    - latency: 7.617671ms
      message: 'load-balancer-api-internal: resolved host name a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:54:08Z"
    - latency: 18.089035ms
      message: 'load-balancer-api-internal: tcp connection to a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:53:08Z"
    - latency: 6.718016ms
      message: 'load-balancer-api-internal: resolved host name a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:53:08Z"
    - latency: 16.258731ms
      message: 'load-balancer-api-internal: tcp connection to a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:52:08Z"
    - latency: 12.31797ms
      message: 'load-balancer-api-internal: resolved host name a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:52:08Z"
    - latency: 13.279085ms
      message: 'load-balancer-api-internal: tcp connection to a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:51:08Z"
    - latency: 7.742919ms
      message: 'load-balancer-api-internal: resolved host name a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:51:08Z"
    - latency: 13.912812ms
      message: 'load-balancer-api-internal: tcp connection to a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:50:08Z"
    - latency: 7.716697ms
      message: 'load-balancer-api-internal: resolved host name a60820e8949964042b361414e30eb88f-4703c05ece5386b8.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:50:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:06:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-102-to-network-check-target-ip-10-0-132-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-102.ec2.internal
      uid: 4cbb28dd-4b1b-47b9-9314-e4c6021ed6dd
    resourceVersion: "113061"
    uid: 04e977b1-b436-47b5-a636-ecde441589c2
  spec:
    sourcePod: network-check-source-6f78d59f99-59msh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:13:08Z"
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.150221ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:55:08Z"
    - latency: 2.186178ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:54:08Z"
    - latency: 2.250319ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:53:08Z"
    - latency: 2.493411ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:52:08Z"
    - latency: 2.217917ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:51:08Z"
    - latency: 2.877546ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:50:08Z"
    - latency: 2.453274ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:49:08Z"
    - latency: 2.59099ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:48:08Z"
    - latency: 2.952666ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:47:08Z"
    - latency: 2.593031ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:46:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:06:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-102-to-network-check-target-ip-10-0-136-244
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-102.ec2.internal
      uid: 4cbb28dd-4b1b-47b9-9314-e4c6021ed6dd
    resourceVersion: "113063"
    uid: d0bd2bba-1561-4de4-805a-d1be75ea8530
  spec:
    sourcePod: network-check-source-6f78d59f99-59msh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:13:08Z"
      message: 'network-check-target-ip-10-0-136-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.20794ms
      message: 'network-check-target-ip-10-0-136-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:55:08Z"
    - latency: 1.846135ms
      message: 'network-check-target-ip-10-0-136-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:54:08Z"
    - latency: 2.351414ms
      message: 'network-check-target-ip-10-0-136-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:53:08Z"
    - latency: 2.15316ms
      message: 'network-check-target-ip-10-0-136-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:52:08Z"
    - latency: 2.524968ms
      message: 'network-check-target-ip-10-0-136-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:51:08Z"
    - latency: 2.768855ms
      message: 'network-check-target-ip-10-0-136-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:50:08Z"
    - latency: 2.858442ms
      message: 'network-check-target-ip-10-0-136-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:49:08Z"
    - latency: 2.48983ms
      message: 'network-check-target-ip-10-0-136-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:48:08Z"
    - latency: 2.354068ms
      message: 'network-check-target-ip-10-0-136-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:47:08Z"
    - latency: 2.72544ms
      message: 'network-check-target-ip-10-0-136-244: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:46:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:06:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-102-to-network-check-target-ip-10-0-140-102
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-102.ec2.internal
      uid: 4cbb28dd-4b1b-47b9-9314-e4c6021ed6dd
    resourceVersion: "113062"
    uid: 7eaff19e-a1cc-48ad-b197-2f06f0ae357d
  spec:
    sourcePod: network-check-source-6f78d59f99-59msh
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:13:08Z"
      message: 'network-check-target-ip-10-0-140-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.117802ms
      message: 'network-check-target-ip-10-0-140-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:55:08Z"
    - latency: 1.124337ms
      message: 'network-check-target-ip-10-0-140-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:54:08Z"
    - latency: 1.001541ms
      message: 'network-check-target-ip-10-0-140-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:53:08Z"
    - latency: 908.24µs
      message: 'network-check-target-ip-10-0-140-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:52:08Z"
    - latency: 993.885µs
      message: 'network-check-target-ip-10-0-140-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:51:08Z"
    - latency: 1.78134ms
      message: 'network-check-target-ip-10-0-140-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:50:08Z"
    - latency: 1.516737ms
      message: 'network-check-target-ip-10-0-140-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:49:08Z"
    - latency: 993.924µs
      message: 'network-check-target-ip-10-0-140-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:48:08Z"
    - latency: 1.254023ms
      message: 'network-check-target-ip-10-0-140-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:47:08Z"
    - latency: 1.581001ms
      message: 'network-check-target-ip-10-0-140-102: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:46:08Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T20:06:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-102-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-102.ec2.internal
      uid: 4cbb28dd-4b1b-47b9-9314-e4c6021ed6dd
    resourceVersion: "112170"
    uid: c7ea7bc1-d4e6-416d-a021-68688152cd57
  spec:
    sourcePod: network-check-source-6f78d59f99-59msh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T20:12:08Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.091948ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:54:08Z"
    - latency: 2.113857ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:54:08Z"
    - latency: 1.151021ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:53:08Z"
    - latency: 1.978563ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:53:08Z"
    - latency: 1.213938ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:52:08Z"
    - latency: 2.015739ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:52:08Z"
    - latency: 1.19087ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:51:08Z"
    - latency: 1.836636ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:51:08Z"
    - latency: 1.018891ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:50:08Z"
    - latency: 2.580735ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:50:08Z"
kind: List
metadata:
  resourceVersion: ""