apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-06T13:53:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-95-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-95.ec2.internal
      uid: 64f3da21-b0d7-4cde-9884-0682966b1c43
    resourceVersion: "32253"
    uid: 6617075e-73de-4aa2-933d-f30621e1aa20
  spec:
    sourcePod: network-check-source-dbd9cf844-mgngd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-06T14:00:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.183519ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:07:57Z"
    - latency: 1.112408ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:06:57Z"
    - latency: 1.185073ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:05:57Z"
    - latency: 1.009427ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:04:57Z"
    - latency: 1.134558ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:03:57Z"
    - latency: 931.963µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:02:57Z"
    - latency: 1.095099ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:01:57Z"
    - latency: 2.38201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:00:57Z"
    - latency: 1.075405ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T13:59:57Z"
    - latency: 1.150967ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T13:58:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-06T13:53:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-95-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-95.ec2.internal
      uid: 64f3da21-b0d7-4cde-9884-0682966b1c43
    resourceVersion: "30397"
    uid: 1fc989c0-cc27-4683-b10e-ca55f87bb4d6
  spec:
    sourcePod: network-check-source-dbd9cf844-mgngd
    targetEndpoint: a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-06T13:59:57Z"
      message: 'load-balancer-api-external: tcp connection to a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.420256ms
      message: 'load-balancer-api-external: tcp connection to a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:05:57Z"
    - latency: 6.797878ms
      message: 'load-balancer-api-external: resolved host name a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:05:57Z"
    - latency: 4.185715ms
      message: 'load-balancer-api-external: tcp connection to a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:04:57Z"
    - latency: 6.634632ms
      message: 'load-balancer-api-external: resolved host name a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:04:57Z"
    - latency: 4.981118ms
      message: 'load-balancer-api-external: tcp connection to a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:03:57Z"
    - latency: 6.963017ms
      message: 'load-balancer-api-external: resolved host name a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:03:57Z"
    - latency: 4.0654ms
      message: 'load-balancer-api-external: tcp connection to a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:02:57Z"
    - latency: 6.585907ms
      message: 'load-balancer-api-external: resolved host name a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:02:57Z"
    - latency: 5.273558ms
      message: 'load-balancer-api-external: tcp connection to a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:01:57Z"
    - latency: 6.584286ms
      message: 'load-balancer-api-external: resolved host name a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:01:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-06T13:53:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-95-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-95.ec2.internal
      uid: 64f3da21-b0d7-4cde-9884-0682966b1c43
    resourceVersion: "30396"
    uid: 3b64d2ab-4fe6-4d25-8d27-19f4361d7e58
  spec:
    sourcePod: network-check-source-dbd9cf844-mgngd
    targetEndpoint: a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-06T13:59:57Z"
      message: 'load-balancer-api-internal: tcp connection to a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.384843ms
      message: 'load-balancer-api-internal: tcp connection to a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:05:57Z"
    - latency: 6.754508ms
      message: 'load-balancer-api-internal: resolved host name a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:05:57Z"
    - latency: 3.984308ms
      message: 'load-balancer-api-internal: tcp connection to a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:04:57Z"
    - latency: 6.663528ms
      message: 'load-balancer-api-internal: resolved host name a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:04:57Z"
    - latency: 5.228655ms
      message: 'load-balancer-api-internal: tcp connection to a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:03:57Z"
    - latency: 6.997143ms
      message: 'load-balancer-api-internal: resolved host name a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:03:57Z"
    - latency: 4.92585ms
      message: 'load-balancer-api-internal: tcp connection to a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:02:57Z"
    - latency: 6.616443ms
      message: 'load-balancer-api-internal: resolved host name a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:02:57Z"
    - latency: 4.887415ms
      message: 'load-balancer-api-internal: tcp connection to a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:01:57Z"
    - latency: 6.617501ms
      message: 'load-balancer-api-internal: resolved host name a89b0f4a330604360bc8c16b21d1b9bb-f30326f3ab4c13b0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:01:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-06T13:53:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-95-to-network-check-target-ip-10-0-131-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-95.ec2.internal
      uid: 64f3da21-b0d7-4cde-9884-0682966b1c43
    resourceVersion: "32250"
    uid: 4e8d0296-14a0-48cc-9e30-9f9f1aa4e5d9
  spec:
    sourcePod: network-check-source-dbd9cf844-mgngd
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-06T14:00:57Z"
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 769.789µs
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:07:57Z"
    - latency: 992.3µs
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:06:57Z"
    - latency: 1.478653ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:05:57Z"
    - latency: 1.359542ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:04:57Z"
    - latency: 995.129µs
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:03:57Z"
    - latency: 951.369µs
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:02:57Z"
    - latency: 1.643077ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:01:57Z"
    - latency: 2.844861ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:00:57Z"
    - latency: 1.078027ms
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T13:59:57Z"
    - latency: 938.262µs
      message: 'network-check-target-ip-10-0-131-95: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T13:58:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-06T13:53:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-95-to-network-check-target-ip-10-0-135-217
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-95.ec2.internal
      uid: 64f3da21-b0d7-4cde-9884-0682966b1c43
    resourceVersion: "32251"
    uid: 6f793801-7b22-48ff-9cac-0de0f770e716
  spec:
    sourcePod: network-check-source-dbd9cf844-mgngd
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-06T14:00:57Z"
      message: 'network-check-target-ip-10-0-135-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.136337ms
      message: 'network-check-target-ip-10-0-135-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:07:57Z"
    - latency: 2.685626ms
      message: 'network-check-target-ip-10-0-135-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:06:57Z"
    - latency: 2.344262ms
      message: 'network-check-target-ip-10-0-135-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:05:57Z"
    - latency: 2.499633ms
      message: 'network-check-target-ip-10-0-135-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:04:57Z"
    - latency: 2.485822ms
      message: 'network-check-target-ip-10-0-135-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:03:57Z"
    - latency: 2.630316ms
      message: 'network-check-target-ip-10-0-135-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:02:57Z"
    - latency: 2.269756ms
      message: 'network-check-target-ip-10-0-135-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:01:57Z"
    - latency: 3.160495ms
      message: 'network-check-target-ip-10-0-135-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:00:57Z"
    - latency: 2.343321ms
      message: 'network-check-target-ip-10-0-135-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T13:59:57Z"
    - latency: 2.531008ms
      message: 'network-check-target-ip-10-0-135-217: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T13:58:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-06T13:53:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-95-to-network-check-target-ip-10-0-139-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-95.ec2.internal
      uid: 64f3da21-b0d7-4cde-9884-0682966b1c43
    resourceVersion: "32252"
    uid: 32d81580-f977-45d5-854f-84ee0795d1b0
  spec:
    sourcePod: network-check-source-dbd9cf844-mgngd
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-06T14:00:57Z"
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.298986ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:07:57Z"
    - latency: 2.393145ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:06:57Z"
    - latency: 2.210037ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:05:57Z"
    - latency: 2.267505ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:04:57Z"
    - latency: 2.607822ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:03:57Z"
    - latency: 2.059536ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:02:57Z"
    - latency: 2.921271ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:01:57Z"
    - latency: 4.084266ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:00:57Z"
    - latency: 2.381563ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T13:59:57Z"
    - latency: 2.366807ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T13:58:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-06T13:53:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-95-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-95.ec2.internal
      uid: 64f3da21-b0d7-4cde-9884-0682966b1c43
    resourceVersion: "30395"
    uid: 1e1a756b-2abd-4d4f-9f53-daffda815e60
  spec:
    sourcePod: network-check-source-dbd9cf844-mgngd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-06T13:59:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 812.784µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:05:57Z"
    - latency: 1.753387ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:05:57Z"
    - latency: 949.407µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:04:57Z"
    - latency: 1.682485ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:04:57Z"
    - latency: 790.714µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:03:57Z"
    - latency: 1.724478ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:03:57Z"
    - latency: 937.549µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:02:57Z"
    - latency: 1.847207ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:02:57Z"
    - latency: 1.268997ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-06T14:01:57Z"
    - latency: 1.957995ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-06T14:01:57Z"
kind: List
metadata:
  resourceVersion: ""