apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:52:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-66-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-66.ec2.internal
      uid: a692d5ba-70c6-40db-ae6e-5c743d58e654
    resourceVersion: "54267"
    uid: a1e59bb0-bf7b-4623-a6ec-37aef7556775
  spec:
    sourcePod: network-check-source-989f8b8dc-mq4f7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:59:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 868.146µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:27:50Z"
    - latency: 831.487µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:26:50Z"
    - latency: 882.103µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:25:50Z"
    - latency: 1.170745ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:24:50Z"
    - latency: 906.674µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:23:50Z"
    - latency: 1.137834ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:22:50Z"
    - latency: 900.81µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:21:50Z"
    - latency: 806.247µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:20:50Z"
    - latency: 1.478323ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:19:50Z"
    - latency: 1.119886ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:18:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:52:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-66-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-66.ec2.internal
      uid: a692d5ba-70c6-40db-ae6e-5c743d58e654
    resourceVersion: "55234"
    uid: afee4587-be2e-416b-a02d-8ef1f90cac39
  spec:
    sourcePod: network-check-source-989f8b8dc-mq4f7
    targetEndpoint: a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:58:50Z"
      message: 'load-balancer-api-external: tcp connection to a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.071852ms
      message: 'load-balancer-api-external: tcp connection to a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:28:50Z"
    - latency: 8.20362ms
      message: 'load-balancer-api-external: resolved host name a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:28:50Z"
    - latency: 7.293171ms
      message: 'load-balancer-api-external: tcp connection to a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:27:50Z"
    - latency: 7.6161ms
      message: 'load-balancer-api-external: resolved host name a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:27:50Z"
    - latency: 3.952002ms
      message: 'load-balancer-api-external: tcp connection to a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:26:50Z"
    - latency: 7.499231ms
      message: 'load-balancer-api-external: resolved host name a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:26:50Z"
    - latency: 4.906741ms
      message: 'load-balancer-api-external: tcp connection to a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:25:50Z"
    - latency: 8.020462ms
      message: 'load-balancer-api-external: resolved host name a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:25:50Z"
    - latency: 6.113696ms
      message: 'load-balancer-api-external: tcp connection to a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:24:50Z"
    - latency: 7.750731ms
      message: 'load-balancer-api-external: resolved host name a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:24:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:52:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-66-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-66.ec2.internal
      uid: a692d5ba-70c6-40db-ae6e-5c743d58e654
    resourceVersion: "55233"
    uid: dfef7818-b3f3-402e-87b3-99a09e26e701
  spec:
    sourcePod: network-check-source-989f8b8dc-mq4f7
    targetEndpoint: a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:58:50Z"
      message: 'load-balancer-api-internal: tcp connection to a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.047339ms
      message: 'load-balancer-api-internal: tcp connection to a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:28:50Z"
    - latency: 8.095883ms
      message: 'load-balancer-api-internal: resolved host name a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:28:50Z"
    - latency: 7.249907ms
      message: 'load-balancer-api-internal: tcp connection to a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:27:50Z"
    - latency: 7.688598ms
      message: 'load-balancer-api-internal: resolved host name a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:27:50Z"
    - latency: 3.953008ms
      message: 'load-balancer-api-internal: tcp connection to a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:26:50Z"
    - latency: 7.390767ms
      message: 'load-balancer-api-internal: resolved host name a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:26:50Z"
    - latency: 4.898442ms
      message: 'load-balancer-api-internal: tcp connection to a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:25:50Z"
    - latency: 8.073639ms
      message: 'load-balancer-api-internal: resolved host name a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:25:50Z"
    - latency: 6.04042ms
      message: 'load-balancer-api-internal: tcp connection to a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:24:50Z"
    - latency: 7.74094ms
      message: 'load-balancer-api-internal: resolved host name a58ec30f57ffa4742b2abb8648db832d-bb19d5387d4c8c1e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:24:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:52:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-66-to-network-check-target-ip-10-0-132-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-66.ec2.internal
      uid: a692d5ba-70c6-40db-ae6e-5c743d58e654
    resourceVersion: "54265"
    uid: a91e6bd6-3721-4a66-a2a2-38d649a03e13
  spec:
    sourcePod: network-check-source-989f8b8dc-mq4f7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:59:50Z"
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.579264ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:27:50Z"
    - latency: 1.893115ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:26:50Z"
    - latency: 2.036581ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:25:50Z"
    - latency: 1.997673ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:24:50Z"
    - latency: 2.011175ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:23:50Z"
    - latency: 2.22373ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:22:50Z"
    - latency: 1.899505ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:21:50Z"
    - latency: 1.943919ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:20:50Z"
    - latency: 2.09134ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:19:50Z"
    - latency: 2.011529ms
      message: 'network-check-target-ip-10-0-132-43: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:18:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:52:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-66-to-network-check-target-ip-10-0-142-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-66.ec2.internal
      uid: a692d5ba-70c6-40db-ae6e-5c743d58e654
    resourceVersion: "54266"
    uid: 7e9a4f31-c93a-401f-9cfa-0cb8698d6eb2
  spec:
    sourcePod: network-check-source-989f8b8dc-mq4f7
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:59:50Z"
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.797555ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:27:50Z"
    - latency: 1.779413ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:26:50Z"
    - latency: 1.978671ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:25:50Z"
    - latency: 2.27711ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:24:50Z"
    - latency: 2.202274ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:23:50Z"
    - latency: 1.879691ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:22:50Z"
    - latency: 1.833254ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:21:50Z"
    - latency: 1.912579ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:20:50Z"
    - latency: 2.238216ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:19:50Z"
    - latency: 1.937447ms
      message: 'network-check-target-ip-10-0-142-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:18:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:52:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-66-to-network-check-target-ip-10-0-142-66
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-66.ec2.internal
      uid: a692d5ba-70c6-40db-ae6e-5c743d58e654
    resourceVersion: "54264"
    uid: c912f5f6-0558-45e7-9414-aaf3d813c659
  spec:
    sourcePod: network-check-source-989f8b8dc-mq4f7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:59:50Z"
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 748.623µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:27:50Z"
    - latency: 823.508µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:26:50Z"
    - latency: 818.005µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:25:50Z"
    - latency: 836.539µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:24:50Z"
    - latency: 955.688µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:23:50Z"
    - latency: 977.789µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:22:50Z"
    - latency: 739.499µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:21:50Z"
    - latency: 799.13µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:20:50Z"
    - latency: 902.582µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:19:50Z"
    - latency: 842.326µs
      message: 'network-check-target-ip-10-0-142-66: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:18:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-07T18:52:49Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-66-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-66.ec2.internal
      uid: a692d5ba-70c6-40db-ae6e-5c743d58e654
    resourceVersion: "55231"
    uid: c94e2d0c-40d5-4183-8523-fbbedfc2b1ad
  spec:
    sourcePod: network-check-source-989f8b8dc-mq4f7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-07T18:58:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 954.175µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:28:50Z"
    - latency: 1.525594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:28:50Z"
    - latency: 1.088269ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:27:50Z"
    - latency: 1.921437ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:27:50Z"
    - latency: 853.526µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:26:50Z"
    - latency: 1.585077ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:26:50Z"
    - latency: 1.223689ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:25:50Z"
    - latency: 1.651954ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:25:50Z"
    - latency: 1.416228ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-07T19:24:50Z"
    - latency: 1.760059ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-07T19:24:50Z"
kind: List
metadata:
  resourceVersion: ""