apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-248-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-248.ec2.internal
      uid: 23d6e673-61b3-4dfb-9472-cd49392e0eb9
    resourceVersion: "64375"
    uid: 2bccbac0-f7b4-498d-97ca-fac52169befb
  spec:
    sourcePod: network-check-source-7d88cb55d8-x7pp5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:49:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.121901ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:24:48Z"
    - latency: 967.754µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:23:48Z"
    - latency: 1.397409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:22:48Z"
    - latency: 1.017785ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:21:48Z"
    - latency: 960.02µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:20:48Z"
    - latency: 824.497µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:19:48Z"
    - latency: 1.400666ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:18:48Z"
    - latency: 1.316477ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:17:48Z"
    - latency: 1.14919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:16:48Z"
    - latency: 1.001768ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:15:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-248-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-248.ec2.internal
      uid: 23d6e673-61b3-4dfb-9472-cd49392e0eb9
    resourceVersion: "64377"
    uid: 0b35b1e0-2b86-4187-9a26-d668d9e4dd1f
  spec:
    sourcePod: network-check-source-7d88cb55d8-x7pp5
    targetEndpoint: a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:48:48Z"
      message: 'load-balancer-api-external: tcp connection to a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.091161ms
      message: 'load-balancer-api-external: tcp connection to a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:24:48Z"
    - latency: 11.224139ms
      message: 'load-balancer-api-external: resolved host name a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:24:48Z"
    - latency: 3.930761ms
      message: 'load-balancer-api-external: tcp connection to a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:23:48Z"
    - latency: 7.078658ms
      message: 'load-balancer-api-external: resolved host name a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:23:48Z"
    - latency: 5.328287ms
      message: 'load-balancer-api-external: tcp connection to a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:22:48Z"
    - latency: 7.390273ms
      message: 'load-balancer-api-external: resolved host name a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:22:48Z"
    - latency: 5.49258ms
      message: 'load-balancer-api-external: tcp connection to a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:21:48Z"
    - latency: 8.176183ms
      message: 'load-balancer-api-external: resolved host name a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:21:48Z"
    - latency: 4.326893ms
      message: 'load-balancer-api-external: tcp connection to a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:20:48Z"
    - latency: 6.925736ms
      message: 'load-balancer-api-external: resolved host name a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:20:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-248-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-248.ec2.internal
      uid: 23d6e673-61b3-4dfb-9472-cd49392e0eb9
    resourceVersion: "64378"
    uid: c5266756-f332-418b-9bb8-55ce3da4faa5
  spec:
    sourcePod: network-check-source-7d88cb55d8-x7pp5
    targetEndpoint: a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:48:48Z"
      message: 'load-balancer-api-internal: tcp connection to a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.875476ms
      message: 'load-balancer-api-internal: tcp connection to a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:24:48Z"
    - latency: 11.216393ms
      message: 'load-balancer-api-internal: resolved host name a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:24:48Z"
    - latency: 4.393014ms
      message: 'load-balancer-api-internal: tcp connection to a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:23:48Z"
    - latency: 7.09179ms
      message: 'load-balancer-api-internal: resolved host name a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:23:48Z"
    - latency: 3.485479ms
      message: 'load-balancer-api-internal: tcp connection to a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:22:48Z"
    - latency: 7.45366ms
      message: 'load-balancer-api-internal: resolved host name a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:22:48Z"
    - latency: 5.472158ms
      message: 'load-balancer-api-internal: tcp connection to a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:21:48Z"
    - latency: 8.257806ms
      message: 'load-balancer-api-internal: resolved host name a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:21:48Z"
    - latency: 4.394894ms
      message: 'load-balancer-api-internal: tcp connection to a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:20:48Z"
    - latency: 6.858236ms
      message: 'load-balancer-api-internal: resolved host name a287ae333da1048269af836e85a5d001-8577c47ee4a4db3d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:20:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-248-to-network-check-target-ip-10-0-138-248
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-248.ec2.internal
      uid: 23d6e673-61b3-4dfb-9472-cd49392e0eb9
    resourceVersion: "64372"
    uid: 22e3966e-b6a5-443c-bc2d-885021638ae4
  spec:
    sourcePod: network-check-source-7d88cb55d8-x7pp5
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:49:48Z"
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 823.028µs
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:24:48Z"
    - latency: 1.12817ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:23:48Z"
    - latency: 976.956µs
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:22:48Z"
    - latency: 858.926µs
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:21:48Z"
    - latency: 1.329367ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:20:48Z"
    - latency: 1.130414ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:19:48Z"
    - latency: 1.192995ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:18:48Z"
    - latency: 1.133419ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:17:48Z"
    - latency: 1.021206ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:16:48Z"
    - latency: 1.46459ms
      message: 'network-check-target-ip-10-0-138-248: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:15:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-248-to-network-check-target-ip-10-0-139-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-248.ec2.internal
      uid: 23d6e673-61b3-4dfb-9472-cd49392e0eb9
    resourceVersion: "64373"
    uid: 4435383a-5c79-40cb-b8a7-e653c6baf249
  spec:
    sourcePod: network-check-source-7d88cb55d8-x7pp5
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:49:48Z"
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.176565ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:24:48Z"
    - latency: 2.079196ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:23:48Z"
    - latency: 2.057259ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:22:48Z"
    - latency: 2.065362ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:21:48Z"
    - latency: 1.885746ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:20:48Z"
    - latency: 1.945676ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:19:48Z"
    - latency: 1.876919ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:18:48Z"
    - latency: 1.954154ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:17:48Z"
    - latency: 1.942199ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:16:48Z"
    - latency: 2.354729ms
      message: 'network-check-target-ip-10-0-139-47: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:15:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-248-to-network-check-target-ip-10-0-143-193
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-248.ec2.internal
      uid: 23d6e673-61b3-4dfb-9472-cd49392e0eb9
    resourceVersion: "64374"
    uid: 13a2c19c-a123-4f97-ab45-e8bee034b948
  spec:
    sourcePod: network-check-source-7d88cb55d8-x7pp5
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:49:48Z"
      message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.3062ms
      message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:24:48Z"
    - latency: 2.406898ms
      message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:23:48Z"
    - latency: 2.457738ms
      message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:22:48Z"
    - latency: 2.586081ms
      message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:21:48Z"
    - latency: 2.240826ms
      message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:20:48Z"
    - latency: 2.43403ms
      message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:19:48Z"
    - latency: 2.336342ms
      message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:18:48Z"
    - latency: 2.545545ms
      message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:17:48Z"
    - latency: 2.394701ms
      message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:16:48Z"
    - latency: 2.589553ms
      message: 'network-check-target-ip-10-0-143-193: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:15:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-24T13:42:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-248-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-248.ec2.internal
      uid: 23d6e673-61b3-4dfb-9472-cd49392e0eb9
    resourceVersion: "64376"
    uid: 1e7c9d57-ff5b-4cc3-97bc-9df12947f5fc
  spec:
    sourcePod: network-check-source-7d88cb55d8-x7pp5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-24T13:48:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.172295ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:24:48Z"
    - latency: 5.714462ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:24:48Z"
    - latency: 1.358205ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:23:48Z"
    - latency: 2.120653ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:23:48Z"
    - latency: 1.15936ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:22:48Z"
    - latency: 1.914608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:22:48Z"
    - latency: 811.735µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:21:48Z"
    - latency: 2.284213ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:21:48Z"
    - latency: 1.220644ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-24T14:20:48Z"
    - latency: 1.726038ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-24T14:20:48Z"
kind: List
metadata:
  resourceVersion: ""