apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:50:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-210-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-210.ec2.internal
      uid: 77f75f7c-2a4f-44ab-b028-b86da28cf57d
    resourceVersion: "32329"
    uid: cedae5e8-7b99-48b8-a15c-b7db1e657a7f
  spec:
    sourcePod: network-check-source-989f8b8dc-l9kx9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:57:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 949.405µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:32:32Z"
    - latency: 764.946µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:31:32Z"
    - latency: 884.698µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:30:32Z"
    - latency: 852.808µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:29:32Z"
    - latency: 949.624µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:28:32Z"
    - latency: 910.61µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:27:32Z"
    - latency: 1.45251ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:26:32Z"
    - latency: 954.074µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:25:32Z"
    - latency: 1.002659ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:24:32Z"
    - latency: 1.042304ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:23:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:50:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-210-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-210.ec2.internal
      uid: 77f75f7c-2a4f-44ab-b028-b86da28cf57d
    resourceVersion: "32330"
    uid: 18ee0056-2c4d-4f27-ae41-de649129b55b
  spec:
    sourcePod: network-check-source-989f8b8dc-l9kx9
    targetEndpoint: a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:56:32Z"
      message: 'load-balancer-api-external: tcp connection to a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.783228ms
      message: 'load-balancer-api-external: tcp connection to a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:32:32Z"
    - latency: 10.300075ms
      message: 'load-balancer-api-external: resolved host name a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:32:32Z"
    - latency: 5.176435ms
      message: 'load-balancer-api-external: tcp connection to a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:31:32Z"
    - latency: 10.36839ms
      message: 'load-balancer-api-external: resolved host name a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:31:32Z"
    - latency: 3.933174ms
      message: 'load-balancer-api-external: tcp connection to a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:30:32Z"
    - latency: 9.159352ms
      message: 'load-balancer-api-external: resolved host name a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:30:32Z"
    - latency: 4.997416ms
      message: 'load-balancer-api-external: tcp connection to a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:29:32Z"
    - latency: 9.293887ms
      message: 'load-balancer-api-external: resolved host name a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:29:32Z"
    - latency: 5.68714ms
      message: 'load-balancer-api-external: tcp connection to a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:28:32Z"
    - latency: 18.36427ms
      message: 'load-balancer-api-external: resolved host name a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:28:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:50:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-210-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-210.ec2.internal
      uid: 77f75f7c-2a4f-44ab-b028-b86da28cf57d
    resourceVersion: "32331"
    uid: 2ba9de64-972a-4cc8-8d63-5567a63713fa
  spec:
    sourcePod: network-check-source-989f8b8dc-l9kx9
    targetEndpoint: a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:56:32Z"
      message: 'load-balancer-api-internal: tcp connection to a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 11.36179ms
      message: 'load-balancer-api-internal: tcp connection to a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:32:32Z"
    - latency: 10.37532ms
      message: 'load-balancer-api-internal: resolved host name a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:32:32Z"
    - latency: 3.875313ms
      message: 'load-balancer-api-internal: tcp connection to a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:31:32Z"
    - latency: 10.481476ms
      message: 'load-balancer-api-internal: resolved host name a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:31:32Z"
    - latency: 5.392197ms
      message: 'load-balancer-api-internal: tcp connection to a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:30:32Z"
    - latency: 9.082071ms
      message: 'load-balancer-api-internal: resolved host name a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:30:32Z"
    - latency: 4.957252ms
      message: 'load-balancer-api-internal: tcp connection to a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:29:32Z"
    - latency: 9.316731ms
      message: 'load-balancer-api-internal: resolved host name a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:29:32Z"
    - latency: 5.710408ms
      message: 'load-balancer-api-internal: tcp connection to a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:28:32Z"
    - latency: 18.323302ms
      message: 'load-balancer-api-internal: resolved host name a14ba1be6e2c14932be3357bb309a308-4839cdf8fb2c7351.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:28:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:50:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-210-to-network-check-target-ip-10-0-136-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-210.ec2.internal
      uid: 77f75f7c-2a4f-44ab-b028-b86da28cf57d
    resourceVersion: "32325"
    uid: 771393ab-e50d-42cc-8630-b0b5d9c6f331
  spec:
    sourcePod: network-check-source-989f8b8dc-l9kx9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:57:32Z"
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.172824ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:32:32Z"
    - latency: 1.814032ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:31:32Z"
    - latency: 1.824774ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:30:32Z"
    - latency: 1.968441ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:29:32Z"
    - latency: 1.677242ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:28:32Z"
    - latency: 1.893205ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:27:32Z"
    - latency: 1.738633ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:26:32Z"
    - latency: 1.831376ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:25:32Z"
    - latency: 1.453663ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:24:32Z"
    - latency: 1.751287ms
      message: 'network-check-target-ip-10-0-136-217: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:23:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:50:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-210-to-network-check-target-ip-10-0-140-210
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-210.ec2.internal
      uid: 77f75f7c-2a4f-44ab-b028-b86da28cf57d
    resourceVersion: "32327"
    uid: a0cf6b7f-d218-4ef9-afa1-046be9fc1da3
  spec:
    sourcePod: network-check-source-989f8b8dc-l9kx9
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:57:32Z"
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.290871ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:32:32Z"
    - latency: 767.742µs
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:31:32Z"
    - latency: 1.236434ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:30:32Z"
    - latency: 765.902µs
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:29:32Z"
    - latency: 889.625µs
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:28:32Z"
    - latency: 961.106µs
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:27:32Z"
    - latency: 851.831µs
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:26:32Z"
    - latency: 979.74µs
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:25:32Z"
    - latency: 907.745µs
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:24:32Z"
    - latency: 1.007952ms
      message: 'network-check-target-ip-10-0-140-210: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:23:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:50:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-210-to-network-check-target-ip-10-0-142-63
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-210.ec2.internal
      uid: 77f75f7c-2a4f-44ab-b028-b86da28cf57d
    resourceVersion: "32326"
    uid: 0ec44e14-2b70-4b2e-907c-98119bae8073
  spec:
    sourcePod: network-check-source-989f8b8dc-l9kx9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:57:32Z"
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.280952ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:32:32Z"
    - latency: 2.244095ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:31:32Z"
    - latency: 2.478714ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:30:32Z"
    - latency: 2.173173ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:29:32Z"
    - latency: 1.868739ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:28:32Z"
    - latency: 2.026857ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:27:32Z"
    - latency: 2.315697ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:26:32Z"
    - latency: 1.995978ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:25:32Z"
    - latency: 2.163176ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:24:32Z"
    - latency: 2.136915ms
      message: 'network-check-target-ip-10-0-142-63: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:23:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T16:50:30Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-210-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-210.ec2.internal
      uid: 77f75f7c-2a4f-44ab-b028-b86da28cf57d
    resourceVersion: "32328"
    uid: 99eb14ba-c3f3-4681-bbf8-e3b06aa890ec
  spec:
    sourcePod: network-check-source-989f8b8dc-l9kx9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T16:56:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 865.148µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:32:32Z"
    - latency: 2.285322ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:32:32Z"
    - latency: 877.843µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:31:32Z"
    - latency: 1.822104ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:31:32Z"
    - latency: 1.083018ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:30:32Z"
    - latency: 1.643314ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:30:32Z"
    - latency: 824.106µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:29:32Z"
    - latency: 1.98402ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:29:32Z"
    - latency: 816.556µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T17:28:32Z"
    - latency: 1.832911ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T17:28:32Z"
kind: List
metadata:
  resourceVersion: ""