apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T20:00:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-80-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-80.ec2.internal
      uid: e7d42cf1-b5b2-4ba5-b750-8e6279e362c6
    resourceVersion: "69203"
    uid: 6219159b-fd5e-4941-9a95-03e92ec77769
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ljksn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T20:07:25Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 955.235µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:49:25Z"
    - latency: 1.148678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:48:25Z"
    - latency: 1.459821ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:47:25Z"
    - latency: 1.028037ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:46:25Z"
    - latency: 1.447417ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:45:25Z"
    - latency: 1.15737ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:44:25Z"
    - latency: 1.108385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:43:25Z"
    - latency: 1.338976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:42:25Z"
    - latency: 1.07279ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:41:25Z"
    - latency: 1.182192ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:40:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T20:00:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-80-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-80.ec2.internal
      uid: e7d42cf1-b5b2-4ba5-b750-8e6279e362c6
    resourceVersion: "68099"
    uid: f2571805-2c72-4c92-a3fb-809eb03ca8ff
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ljksn
    targetEndpoint: acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T20:06:25Z"
      message: 'load-balancer-api-external: tcp connection to acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.811008ms
      message: 'load-balancer-api-external: tcp connection to acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:48:25Z"
    - latency: 8.000545ms
      message: 'load-balancer-api-external: resolved host name acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:48:25Z"
    - latency: 5.254613ms
      message: 'load-balancer-api-external: tcp connection to acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:47:25Z"
    - latency: 8.536113ms
      message: 'load-balancer-api-external: resolved host name acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:47:25Z"
    - latency: 4.153605ms
      message: 'load-balancer-api-external: tcp connection to acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:46:25Z"
    - latency: 7.249109ms
      message: 'load-balancer-api-external: resolved host name acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:46:25Z"
    - latency: 5.174345ms
      message: 'load-balancer-api-external: tcp connection to acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:45:25Z"
    - latency: 8.31697ms
      message: 'load-balancer-api-external: resolved host name acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:45:25Z"
    - latency: 5.320447ms
      message: 'load-balancer-api-external: tcp connection to acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:44:25Z"
    - latency: 8.093806ms
      message: 'load-balancer-api-external: resolved host name acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:44:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T20:00:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-80-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-80.ec2.internal
      uid: e7d42cf1-b5b2-4ba5-b750-8e6279e362c6
    resourceVersion: "68098"
    uid: 14fbbf16-d492-48ec-b797-54bff34f7c5a
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ljksn
    targetEndpoint: acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T20:06:25Z"
      message: 'load-balancer-api-internal: tcp connection to acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.471409ms
      message: 'load-balancer-api-internal: tcp connection to acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:48:25Z"
    - latency: 8.064607ms
      message: 'load-balancer-api-internal: resolved host name acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:48:25Z"
    - latency: 4.486622ms
      message: 'load-balancer-api-internal: tcp connection to acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:47:25Z"
    - latency: 8.622935ms
      message: 'load-balancer-api-internal: resolved host name acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:47:25Z"
    - latency: 3.49834ms
      message: 'load-balancer-api-internal: tcp connection to acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:46:25Z"
    - latency: 7.337126ms
      message: 'load-balancer-api-internal: resolved host name acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:46:25Z"
    - latency: 5.128636ms
      message: 'load-balancer-api-internal: tcp connection to acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:45:25Z"
    - latency: 8.399027ms
      message: 'load-balancer-api-internal: resolved host name acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:45:25Z"
    - latency: 5.373007ms
      message: 'load-balancer-api-internal: tcp connection to acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:44:25Z"
    - latency: 8.076834ms
      message: 'load-balancer-api-internal: resolved host name acff40dcd9d5f4bca86860bacb44ba33-2c0d2d0832d429e0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:44:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T20:00:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-80-to-network-check-target-ip-10-0-141-177
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-80.ec2.internal
      uid: e7d42cf1-b5b2-4ba5-b750-8e6279e362c6
    resourceVersion: "69202"
    uid: 035d92d5-3604-4c46-b4de-c99b3f9245f2
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ljksn
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T20:07:25Z"
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.941477ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:49:25Z"
    - latency: 1.957491ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:48:25Z"
    - latency: 2.233121ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:47:25Z"
    - latency: 2.473399ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:46:25Z"
    - latency: 2.223671ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:45:25Z"
    - latency: 1.835761ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:44:25Z"
    - latency: 1.868922ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:43:25Z"
    - latency: 2.195538ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:42:25Z"
    - latency: 1.849413ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:41:25Z"
    - latency: 2.122437ms
      message: 'network-check-target-ip-10-0-141-177: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:40:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T20:00:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-80-to-network-check-target-ip-10-0-142-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-80.ec2.internal
      uid: e7d42cf1-b5b2-4ba5-b750-8e6279e362c6
    resourceVersion: "69200"
    uid: 499cd318-2e53-4b68-a6e5-d881d946db7c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ljksn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T20:07:25Z"
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.041745ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:49:25Z"
    - latency: 827.66µs
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:48:25Z"
    - latency: 1.482227ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:47:25Z"
    - latency: 1.183092ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:46:25Z"
    - latency: 1.631783ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:45:25Z"
    - latency: 830.193µs
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:44:25Z"
    - latency: 1.235514ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:43:25Z"
    - latency: 1.004989ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:42:25Z"
    - latency: 941.287µs
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:41:25Z"
    - latency: 1.030492ms
      message: 'network-check-target-ip-10-0-142-80: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:40:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T20:00:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-80-to-network-check-target-ip-10-0-143-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-80.ec2.internal
      uid: e7d42cf1-b5b2-4ba5-b750-8e6279e362c6
    resourceVersion: "69201"
    uid: 016457a8-5d75-46bc-b33b-e86ea875b64b
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ljksn
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T20:07:25Z"
      message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.084883ms
      message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:49:25Z"
    - latency: 2.235487ms
      message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:48:25Z"
    - latency: 2.20974ms
      message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:47:25Z"
    - latency: 2.322625ms
      message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:46:25Z"
    - latency: 2.264947ms
      message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:45:25Z"
    - latency: 2.023979ms
      message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:44:25Z"
    - latency: 1.822886ms
      message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:43:25Z"
    - latency: 2.253364ms
      message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:42:25Z"
    - latency: 1.833566ms
      message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:41:25Z"
    - latency: 2.207422ms
      message: 'network-check-target-ip-10-0-143-185: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:40:25Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-17T20:00:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-80-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-80.ec2.internal
      uid: e7d42cf1-b5b2-4ba5-b750-8e6279e362c6
    resourceVersion: "68097"
    uid: 5137f13c-d4fa-4b8f-8c81-2f73126dc1bf
  spec:
    sourcePod: network-check-source-7bc5b6bf85-ljksn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-17T20:06:25Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 937.714µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:48:25Z"
    - latency: 1.80142ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:48:25Z"
    - latency: 1.117506ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:47:25Z"
    - latency: 1.714706ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:47:25Z"
    - latency: 968.383µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:46:25Z"
    - latency: 1.750214ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:46:25Z"
    - latency: 882.18µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:45:25Z"
    - latency: 2.30517ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:45:25Z"
    - latency: 847.517µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-17T20:44:25Z"
    - latency: 2.189056ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-17T20:44:25Z"
kind: List
metadata:
  resourceVersion: ""