apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 24e90ca6-2a41-4b2b-b140-3c20592f3672
    resourceVersion: "64463"
    uid: 40dbdc6b-367f-4eaf-bf35-7e3ea5270a37
  spec:
    sourcePod: network-check-source-7d88cb55d8-4vl9k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T12:28:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.290223ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:03:51Z"
    - latency: 1.087464ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:02:51Z"
    - latency: 1.4919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:01:51Z"
    - latency: 1.106433ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:00:51Z"
    - latency: 1.264364ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:59:51Z"
    - latency: 1.161516ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:58:51Z"
    - latency: 1.039286ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:57:51Z"
    - latency: 755.884µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:56:51Z"
    - latency: 1.150717ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:55:51Z"
    - latency: 1.12887ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:54:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 24e90ca6-2a41-4b2b-b140-3c20592f3672
    resourceVersion: "64465"
    uid: 6312eb54-6341-4233-a588-0f4d69b7a2e8
  spec:
    sourcePod: network-check-source-7d88cb55d8-4vl9k
    targetEndpoint: a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T12:27:51Z"
      message: 'load-balancer-api-external: tcp connection to a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.056439ms
      message: 'load-balancer-api-external: tcp connection to a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:03:51Z"
    - latency: 10.260908ms
      message: 'load-balancer-api-external: resolved host name a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:03:51Z"
    - latency: 5.113125ms
      message: 'load-balancer-api-external: tcp connection to a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:02:51Z"
    - latency: 14.444152ms
      message: 'load-balancer-api-external: resolved host name a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:02:51Z"
    - latency: 3.91136ms
      message: 'load-balancer-api-external: tcp connection to a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:01:51Z"
    - latency: 13.894278ms
      message: 'load-balancer-api-external: resolved host name a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:01:51Z"
    - latency: 5.808795ms
      message: 'load-balancer-api-external: tcp connection to a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:00:51Z"
    - latency: 9.664872ms
      message: 'load-balancer-api-external: resolved host name a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:00:51Z"
    - latency: 6.242108ms
      message: 'load-balancer-api-external: tcp connection to a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:59:51Z"
    - latency: 16.943586ms
      message: 'load-balancer-api-external: resolved host name a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:59:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 24e90ca6-2a41-4b2b-b140-3c20592f3672
    resourceVersion: "64464"
    uid: f7fe41a2-36b1-48e3-89b6-4b534a04c0dd
  spec:
    sourcePod: network-check-source-7d88cb55d8-4vl9k
    targetEndpoint: a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T12:27:51Z"
      message: 'load-balancer-api-internal: tcp connection to a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.599323ms
      message: 'load-balancer-api-internal: tcp connection to a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:03:51Z"
    - latency: 10.317348ms
      message: 'load-balancer-api-internal: resolved host name a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:03:51Z"
    - latency: 5.07398ms
      message: 'load-balancer-api-internal: tcp connection to a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:02:51Z"
    - latency: 14.58712ms
      message: 'load-balancer-api-internal: resolved host name a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:02:51Z"
    - latency: 4.057275ms
      message: 'load-balancer-api-internal: tcp connection to a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:01:51Z"
    - latency: 13.918673ms
      message: 'load-balancer-api-internal: resolved host name a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:01:51Z"
    - latency: 5.866829ms
      message: 'load-balancer-api-internal: tcp connection to a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:00:51Z"
    - latency: 9.725362ms
      message: 'load-balancer-api-internal: resolved host name a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:00:51Z"
    - latency: 5.35568ms
      message: 'load-balancer-api-internal: tcp connection to a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:59:51Z"
    - latency: 16.894748ms
      message: 'load-balancer-api-internal: resolved host name a6712a21bebc84eb28fd7164110ed05d-d1dd8cac895a2939.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:59:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-128-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 24e90ca6-2a41-4b2b-b140-3c20592f3672
    resourceVersion: "64460"
    uid: bcbb4857-601f-4d7c-aabe-28fefbd6c41a
  spec:
    sourcePod: network-check-source-7d88cb55d8-4vl9k
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T12:28:51Z"
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.432839ms
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:03:51Z"
    - latency: 2.429432ms
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:02:51Z"
    - latency: 2.340791ms
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:01:51Z"
    - latency: 2.17681ms
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:00:51Z"
    - latency: 2.20526ms
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:59:51Z"
    - latency: 2.388393ms
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:58:51Z"
    - latency: 2.156141ms
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:57:51Z"
    - latency: 2.36788ms
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:56:51Z"
    - latency: 2.144012ms
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:55:51Z"
    - latency: 2.212391ms
      message: 'network-check-target-ip-10-0-128-194: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:54:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-132-126
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 24e90ca6-2a41-4b2b-b140-3c20592f3672
    resourceVersion: "64461"
    uid: 28d9237f-542b-4354-97d2-189301090923
  spec:
    sourcePod: network-check-source-7d88cb55d8-4vl9k
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T12:28:51Z"
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.384145ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:03:51Z"
    - latency: 2.29423ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:02:51Z"
    - latency: 2.307468ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:01:51Z"
    - latency: 2.348065ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:00:51Z"
    - latency: 2.414561ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:59:51Z"
    - latency: 2.248372ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:58:51Z"
    - latency: 2.231037ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:57:51Z"
    - latency: 2.137169ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:56:51Z"
    - latency: 2.640256ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:55:51Z"
    - latency: 2.362855ms
      message: 'network-check-target-ip-10-0-132-126: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:54:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-140-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 24e90ca6-2a41-4b2b-b140-3c20592f3672
    resourceVersion: "64459"
    uid: f675d51b-82cf-4fc1-a755-c193d45ee5e9
  spec:
    sourcePod: network-check-source-7d88cb55d8-4vl9k
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T12:28:51Z"
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 953.997µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:03:51Z"
    - latency: 1.154182ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:02:51Z"
    - latency: 788.408µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:01:51Z"
    - latency: 768.077µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:00:51Z"
    - latency: 876.2µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:59:51Z"
    - latency: 1.359809ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:58:51Z"
    - latency: 933.537µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:57:51Z"
    - latency: 994.724µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:56:51Z"
    - latency: 847.105µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:55:51Z"
    - latency: 925.396µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:54:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T12:21:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 24e90ca6-2a41-4b2b-b140-3c20592f3672
    resourceVersion: "64462"
    uid: ef666605-3e06-4aa9-83a7-38f05ec7c4f8
  spec:
    sourcePod: network-check-source-7d88cb55d8-4vl9k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T12:27:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.040564ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:03:51Z"
    - latency: 1.844445ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:03:51Z"
    - latency: 1.329151ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:02:51Z"
    - latency: 2.063289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:02:51Z"
    - latency: 1.049616ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:01:51Z"
    - latency: 2.406581ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:01:51Z"
    - latency: 950.266µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T13:00:51Z"
    - latency: 1.714213ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T13:00:51Z"
    - latency: 958.045µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T12:59:51Z"
    - latency: 2.071245ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T12:59:51Z"
kind: List
metadata:
  resourceVersion: ""