apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: 11deca0f-3e83-467b-afd5-910046d245b0
    resourceVersion: "43826"
    uid: dd9088e9-301c-409f-974a-b8b201d144c2
  spec:
    sourcePod: network-check-source-dbd9cf844-2mqkc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:54:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 903.16µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:15:23Z"
    - latency: 861.469µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:14:23Z"
    - latency: 1.30131ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:13:23Z"
    - latency: 912.275µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:12:23Z"
    - latency: 1.20594ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:11:23Z"
    - latency: 828.21µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:10:23Z"
    - latency: 1.358377ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:09:23Z"
    - latency: 1.054703ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:08:23Z"
    - latency: 1.132382ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:07:23Z"
    - latency: 1.54124ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:06:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: 11deca0f-3e83-467b-afd5-910046d245b0
    resourceVersion: "45940"
    uid: 818ddf7d-6c42-45cf-82e9-dd6628f61edc
  spec:
    sourcePod: network-check-source-dbd9cf844-2mqkc
    targetEndpoint: a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:53:23Z"
      message: 'load-balancer-api-external: tcp connection to a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.032141ms
      message: 'load-balancer-api-external: tcp connection to a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:17:23Z"
    - latency: 7.657404ms
      message: 'load-balancer-api-external: resolved host name a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:17:23Z"
    - latency: 4.39403ms
      message: 'load-balancer-api-external: tcp connection to a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:16:23Z"
    - latency: 8.680242ms
      message: 'load-balancer-api-external: resolved host name a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:16:23Z"
    - latency: 4.765483ms
      message: 'load-balancer-api-external: tcp connection to a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:15:23Z"
    - latency: 8.29363ms
      message: 'load-balancer-api-external: resolved host name a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:15:23Z"
    - latency: 3.775933ms
      message: 'load-balancer-api-external: tcp connection to a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:14:23Z"
    - latency: 8.533427ms
      message: 'load-balancer-api-external: resolved host name a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:14:23Z"
    - latency: 3.802727ms
      message: 'load-balancer-api-external: tcp connection to a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:13:23Z"
    - latency: 7.875265ms
      message: 'load-balancer-api-external: resolved host name a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:13:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: 11deca0f-3e83-467b-afd5-910046d245b0
    resourceVersion: "45941"
    uid: 6cb2dc27-7c4b-426c-91d8-6461585ff301
  spec:
    sourcePod: network-check-source-dbd9cf844-2mqkc
    targetEndpoint: a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:53:23Z"
      message: 'load-balancer-api-internal: tcp connection to a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.080192ms
      message: 'load-balancer-api-internal: tcp connection to a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:17:23Z"
    - latency: 7.635004ms
      message: 'load-balancer-api-internal: resolved host name a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:17:23Z"
    - latency: 4.390343ms
      message: 'load-balancer-api-internal: tcp connection to a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:16:23Z"
    - latency: 8.629979ms
      message: 'load-balancer-api-internal: resolved host name a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:16:23Z"
    - latency: 4.264438ms
      message: 'load-balancer-api-internal: tcp connection to a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:15:23Z"
    - latency: 8.280945ms
      message: 'load-balancer-api-internal: resolved host name a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:15:23Z"
    - latency: 4.261453ms
      message: 'load-balancer-api-internal: tcp connection to a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:14:23Z"
    - latency: 8.48313ms
      message: 'load-balancer-api-internal: resolved host name a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:14:23Z"
    - latency: 3.935157ms
      message: 'load-balancer-api-internal: tcp connection to a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:13:23Z"
    - latency: 7.843956ms
      message: 'load-balancer-api-internal: resolved host name a3536c80f4256499a870d4c6760bd5e0-bf78dff477a96a9e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:13:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-network-check-target-ip-10-0-130-95
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: 11deca0f-3e83-467b-afd5-910046d245b0
    resourceVersion: "43823"
    uid: 9a8f14e6-1c32-482b-b655-1750cd51708b
  spec:
    sourcePod: network-check-source-dbd9cf844-2mqkc
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:54:23Z"
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 831.655µs
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:15:23Z"
    - latency: 837.411µs
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:14:23Z"
    - latency: 1.53689ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:13:23Z"
    - latency: 828.732µs
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:12:23Z"
    - latency: 855.514µs
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:11:23Z"
    - latency: 1.082508ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:10:23Z"
    - latency: 1.20811ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:09:23Z"
    - latency: 877.855µs
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:08:23Z"
    - latency: 1.340833ms
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:07:23Z"
    - latency: 966.043µs
      message: 'network-check-target-ip-10-0-130-95: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:06:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-network-check-target-ip-10-0-140-46
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: 11deca0f-3e83-467b-afd5-910046d245b0
    resourceVersion: "43824"
    uid: ad119d7b-f8f8-4bd0-ba61-c4bebc3103d8
  spec:
    sourcePod: network-check-source-dbd9cf844-2mqkc
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:54:23Z"
      message: 'network-check-target-ip-10-0-140-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.058608ms
      message: 'network-check-target-ip-10-0-140-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:15:23Z"
    - latency: 2.235017ms
      message: 'network-check-target-ip-10-0-140-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:14:23Z"
    - latency: 2.389188ms
      message: 'network-check-target-ip-10-0-140-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:13:23Z"
    - latency: 2.162277ms
      message: 'network-check-target-ip-10-0-140-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:12:23Z"
    - latency: 2.052176ms
      message: 'network-check-target-ip-10-0-140-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:11:23Z"
    - latency: 2.168732ms
      message: 'network-check-target-ip-10-0-140-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:10:23Z"
    - latency: 2.139981ms
      message: 'network-check-target-ip-10-0-140-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:09:23Z"
    - latency: 2.159486ms
      message: 'network-check-target-ip-10-0-140-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:08:23Z"
    - latency: 2.264565ms
      message: 'network-check-target-ip-10-0-140-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:07:23Z"
    - latency: 2.468162ms
      message: 'network-check-target-ip-10-0-140-46: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:06:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-network-check-target-ip-10-0-141-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: 11deca0f-3e83-467b-afd5-910046d245b0
    resourceVersion: "43825"
    uid: 9905edce-859a-4e21-9cf0-16464a27c953
  spec:
    sourcePod: network-check-source-dbd9cf844-2mqkc
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:54:23Z"
      message: 'network-check-target-ip-10-0-141-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.008473ms
      message: 'network-check-target-ip-10-0-141-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:15:23Z"
    - latency: 1.875772ms
      message: 'network-check-target-ip-10-0-141-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:14:23Z"
    - latency: 1.926811ms
      message: 'network-check-target-ip-10-0-141-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:13:23Z"
    - latency: 1.68095ms
      message: 'network-check-target-ip-10-0-141-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:12:23Z"
    - latency: 1.93237ms
      message: 'network-check-target-ip-10-0-141-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:11:23Z"
    - latency: 2.010188ms
      message: 'network-check-target-ip-10-0-141-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:10:23Z"
    - latency: 1.715562ms
      message: 'network-check-target-ip-10-0-141-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:09:23Z"
    - latency: 1.819457ms
      message: 'network-check-target-ip-10-0-141-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:08:23Z"
    - latency: 1.899312ms
      message: 'network-check-target-ip-10-0-141-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:07:23Z"
    - latency: 2.036843ms
      message: 'network-check-target-ip-10-0-141-116: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:06:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-08T13:47:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-95-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-95.ec2.internal
      uid: 11deca0f-3e83-467b-afd5-910046d245b0
    resourceVersion: "45938"
    uid: 02efb4a6-d129-4d66-ac5a-bb676448cb75
  spec:
    sourcePod: network-check-source-dbd9cf844-2mqkc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-08T13:53:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 946.231µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:17:23Z"
    - latency: 1.732368ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:17:23Z"
    - latency: 920.052µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:16:23Z"
    - latency: 2.085599ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:16:23Z"
    - latency: 1.17637ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:15:23Z"
    - latency: 1.766668ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:15:23Z"
    - latency: 854.424µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:14:23Z"
    - latency: 1.962646ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:14:23Z"
    - latency: 957.1µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-08T14:13:23Z"
    - latency: 1.80796ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-08T14:13:23Z"
kind: List
metadata:
  resourceVersion: ""