apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T15:17:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-26-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-26.ec2.internal
      uid: e40e663d-9607-4f5e-8591-cabd75ec413f
    resourceVersion: "56537"
    uid: 73fb7624-d6a2-4144-acfc-4e39358e8d3d
  spec:
    sourcePod: network-check-source-869dcfcdcd-lxhzh
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T15:24:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.026919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:52:36Z"
    - latency: 1.177815ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:51:36Z"
    - latency: 895.93µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:50:36Z"
    - latency: 1.478046ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:49:36Z"
    - latency: 1.086494ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:48:36Z"
    - latency: 1.119248ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:47:36Z"
    - latency: 862.225µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:46:36Z"
    - latency: 2.265479ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:45:36Z"
    - latency: 816.114µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:44:36Z"
    - latency: 1.051564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:43:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T15:17:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-26-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-26.ec2.internal
      uid: e40e663d-9607-4f5e-8591-cabd75ec413f
    resourceVersion: "57495"
    uid: 7a93ca1a-ec8b-4fa7-b69e-bce7d761c070
  spec:
    sourcePod: network-check-source-869dcfcdcd-lxhzh
    targetEndpoint: a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T15:23:36Z"
      message: 'load-balancer-api-external: tcp connection to a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.472577ms
      message: 'load-balancer-api-external: tcp connection to a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:53:36Z"
    - latency: 8.040445ms
      message: 'load-balancer-api-external: resolved host name a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:53:36Z"
    - latency: 6.102607ms
      message: 'load-balancer-api-external: tcp connection to a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:52:36Z"
    - latency: 8.161701ms
      message: 'load-balancer-api-external: resolved host name a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:52:36Z"
    - latency: 5.275789ms
      message: 'load-balancer-api-external: tcp connection to a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:51:36Z"
    - latency: 8.71013ms
      message: 'load-balancer-api-external: resolved host name a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:51:36Z"
    - latency: 3.506508ms
      message: 'load-balancer-api-external: tcp connection to a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:50:36Z"
    - latency: 9.158036ms
      message: 'load-balancer-api-external: resolved host name a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:50:36Z"
    - latency: 4.176574ms
      message: 'load-balancer-api-external: tcp connection to a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:49:36Z"
    - latency: 8.097424ms
      message: 'load-balancer-api-external: resolved host name a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:49:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T15:17:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-26-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-26.ec2.internal
      uid: e40e663d-9607-4f5e-8591-cabd75ec413f
    resourceVersion: "57494"
    uid: f59b58ee-ea15-4c01-ade9-3bbcd32b64a5
  spec:
    sourcePod: network-check-source-869dcfcdcd-lxhzh
    targetEndpoint: a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T15:23:36Z"
      message: 'load-balancer-api-internal: tcp connection to a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.522574ms
      message: 'load-balancer-api-internal: tcp connection to a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:53:36Z"
    - latency: 8.167119ms
      message: 'load-balancer-api-internal: resolved host name a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:53:36Z"
    - latency: 6.154754ms
      message: 'load-balancer-api-internal: tcp connection to a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:52:36Z"
    - latency: 8.189897ms
      message: 'load-balancer-api-internal: resolved host name a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:52:36Z"
    - latency: 5.244371ms
      message: 'load-balancer-api-internal: tcp connection to a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:51:36Z"
    - latency: 8.773832ms
      message: 'load-balancer-api-internal: resolved host name a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:51:36Z"
    - latency: 5.027184ms
      message: 'load-balancer-api-internal: tcp connection to a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:50:36Z"
    - latency: 9.191619ms
      message: 'load-balancer-api-internal: resolved host name a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:50:36Z"
    - latency: 4.200227ms
      message: 'load-balancer-api-internal: tcp connection to a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:49:36Z"
    - latency: 8.148633ms
      message: 'load-balancer-api-internal: resolved host name a2ac0a517fa9f4d00aa2b5c7d610b4f7-2bf485b6a55e1366.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:49:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T15:17:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-26-to-network-check-target-ip-10-0-130-26
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-26.ec2.internal
      uid: e40e663d-9607-4f5e-8591-cabd75ec413f
    resourceVersion: "56534"
    uid: 6699c952-06e4-4a54-bba3-c96ff54b852a
  spec:
    sourcePod: network-check-source-869dcfcdcd-lxhzh
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T15:24:36Z"
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.331708ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:52:36Z"
    - latency: 801.87µs
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:51:36Z"
    - latency: 819.719µs
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:50:36Z"
    - latency: 731.563µs
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:49:36Z"
    - latency: 1.066793ms
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:48:36Z"
    - latency: 923.956µs
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:47:36Z"
    - latency: 830.152µs
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:46:36Z"
    - latency: 970.685µs
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:45:36Z"
    - latency: 950.915µs
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:44:36Z"
    - latency: 901.748µs
      message: 'network-check-target-ip-10-0-130-26: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:43:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T15:17:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-26-to-network-check-target-ip-10-0-138-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-26.ec2.internal
      uid: e40e663d-9607-4f5e-8591-cabd75ec413f
    resourceVersion: "56536"
    uid: f050005d-5173-4cf3-8bb1-8a9d3f467f00
  spec:
    sourcePod: network-check-source-869dcfcdcd-lxhzh
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T15:24:36Z"
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.102968ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:52:36Z"
    - latency: 2.240148ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:51:36Z"
    - latency: 2.245121ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:50:36Z"
    - latency: 2.363785ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:49:36Z"
    - latency: 2.221881ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:48:36Z"
    - latency: 2.474572ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:47:36Z"
    - latency: 2.162765ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:46:36Z"
    - latency: 3.021056ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:45:36Z"
    - latency: 1.802713ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:44:36Z"
    - latency: 2.371628ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:43:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T15:17:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-26-to-network-check-target-ip-10-0-142-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-26.ec2.internal
      uid: e40e663d-9607-4f5e-8591-cabd75ec413f
    resourceVersion: "56535"
    uid: b6a79aac-d23d-4a6e-bf6b-b1139c473740
  spec:
    sourcePod: network-check-source-869dcfcdcd-lxhzh
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T15:24:36Z"
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.688048ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:52:36Z"
    - latency: 1.942385ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:51:36Z"
    - latency: 1.758392ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:50:36Z"
    - latency: 1.795686ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:49:36Z"
    - latency: 1.864166ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:48:36Z"
    - latency: 1.952359ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:47:36Z"
    - latency: 1.688413ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:46:36Z"
    - latency: 3.118159ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:45:36Z"
    - latency: 1.801914ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:44:36Z"
    - latency: 1.964447ms
      message: 'network-check-target-ip-10-0-142-238: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:43:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-12T15:17:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-26-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-26.ec2.internal
      uid: e40e663d-9607-4f5e-8591-cabd75ec413f
    resourceVersion: "57493"
    uid: a4104da7-2fe4-40c1-b5fb-1568a04f03b7
  spec:
    sourcePod: network-check-source-869dcfcdcd-lxhzh
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-12T15:23:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 769.753µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:53:36Z"
    - latency: 1.740016ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:53:36Z"
    - latency: 971.633µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:52:36Z"
    - latency: 2.326658ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:52:36Z"
    - latency: 1.02325ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:51:36Z"
    - latency: 1.834262ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:51:36Z"
    - latency: 985.302µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:50:36Z"
    - latency: 1.679936ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:50:36Z"
    - latency: 888.401µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-12T15:49:36Z"
    - latency: 1.741686ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-12T15:49:36Z"
kind: List
metadata:
  resourceVersion: ""