apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T22:17:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-127-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-127.ec2.internal
      uid: abb0a167-1e61-4526-84ad-048505f99241
    resourceVersion: "59767"
    uid: 1701a4fc-1b4c-4a07-9ecf-0ae36ac48b17
  spec:
    sourcePod: network-check-source-989f8b8dc-phfph
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T22:24:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.185831ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:59:06Z"
    - latency: 939.53µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:58:06Z"
    - latency: 1.090754ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:57:06Z"
    - latency: 888.879µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:56:06Z"
    - latency: 865.573µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:55:06Z"
    - latency: 899.858µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:54:06Z"
    - latency: 1.138099ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:53:06Z"
    - latency: 811.724µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:52:06Z"
    - latency: 911.412µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:51:06Z"
    - latency: 795.008µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:50:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T22:17:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-127-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-127.ec2.internal
      uid: abb0a167-1e61-4526-84ad-048505f99241
    resourceVersion: "59768"
    uid: 736bef11-39c4-4f03-8665-0e9dd429af16
  spec:
    sourcePod: network-check-source-989f8b8dc-phfph
    targetEndpoint: abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T22:23:06Z"
      message: 'load-balancer-api-external: tcp connection to abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.413854ms
      message: 'load-balancer-api-external: tcp connection to abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:59:06Z"
    - latency: 9.020533ms
      message: 'load-balancer-api-external: resolved host name abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:59:06Z"
    - latency: 4.041623ms
      message: 'load-balancer-api-external: tcp connection to abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:58:06Z"
    - latency: 8.617538ms
      message: 'load-balancer-api-external: resolved host name abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:58:06Z"
    - latency: 4.719836ms
      message: 'load-balancer-api-external: tcp connection to abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:57:06Z"
    - latency: 8.383865ms
      message: 'load-balancer-api-external: resolved host name abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:57:06Z"
    - latency: 4.682628ms
      message: 'load-balancer-api-external: tcp connection to abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:56:06Z"
    - latency: 13.145068ms
      message: 'load-balancer-api-external: resolved host name abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:56:06Z"
    - latency: 4.838591ms
      message: 'load-balancer-api-external: tcp connection to abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:55:06Z"
    - latency: 7.313405ms
      message: 'load-balancer-api-external: resolved host name abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:55:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T22:17:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-127-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-127.ec2.internal
      uid: abb0a167-1e61-4526-84ad-048505f99241
    resourceVersion: "59769"
    uid: 645536a5-38b9-4838-aabb-0be8f4ebfc74
  spec:
    sourcePod: network-check-source-989f8b8dc-phfph
    targetEndpoint: abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T22:23:06Z"
      message: 'load-balancer-api-internal: tcp connection to abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.448551ms
      message: 'load-balancer-api-internal: tcp connection to abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:59:06Z"
    - latency: 9.09393ms
      message: 'load-balancer-api-internal: resolved host name abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:59:06Z"
    - latency: 6.337531ms
      message: 'load-balancer-api-internal: tcp connection to abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:58:06Z"
    - latency: 8.648777ms
      message: 'load-balancer-api-internal: resolved host name abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:58:06Z"
    - latency: 4.43479ms
      message: 'load-balancer-api-internal: tcp connection to abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:57:06Z"
    - latency: 8.412745ms
      message: 'load-balancer-api-internal: resolved host name abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:57:06Z"
    - latency: 4.078001ms
      message: 'load-balancer-api-internal: tcp connection to abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:56:06Z"
    - latency: 13.163685ms
      message: 'load-balancer-api-internal: resolved host name abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:56:06Z"
    - latency: 4.85893ms
      message: 'load-balancer-api-internal: tcp connection to abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:55:06Z"
    - latency: 7.261704ms
      message: 'load-balancer-api-internal: resolved host name abca5a74a6db54b26ad444fdc93d3b2e-755fb7d3c6f92b1c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:55:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T22:17:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-127-to-network-check-target-ip-10-0-130-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-127.ec2.internal
      uid: abb0a167-1e61-4526-84ad-048505f99241
    resourceVersion: "59763"
    uid: 9ef4d997-9d6f-4bd2-a252-866503f53964
  spec:
    sourcePod: network-check-source-989f8b8dc-phfph
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T22:24:06Z"
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.138µs
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:59:06Z"
    - latency: 1.011746ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:58:06Z"
    - latency: 1.33484ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:57:06Z"
    - latency: 1.26763ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:56:06Z"
    - latency: 1.261351ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:55:06Z"
    - latency: 765.3µs
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:54:06Z"
    - latency: 1.088533ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:53:06Z"
    - latency: 1.48642ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:52:06Z"
    - latency: 1.208159ms
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:51:06Z"
    - latency: 728.856µs
      message: 'network-check-target-ip-10-0-130-127: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:50:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T22:17:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-127-to-network-check-target-ip-10-0-136-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-127.ec2.internal
      uid: abb0a167-1e61-4526-84ad-048505f99241
    resourceVersion: "59764"
    uid: 0d3bae30-7b23-466a-adb5-501b5cfcc457
  spec:
    sourcePod: network-check-source-989f8b8dc-phfph
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T22:24:06Z"
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.845029ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:59:06Z"
    - latency: 1.73996ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:58:06Z"
    - latency: 1.599956ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:57:06Z"
    - latency: 1.833339ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:56:06Z"
    - latency: 1.589125ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:55:06Z"
    - latency: 1.504972ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:54:06Z"
    - latency: 1.749086ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:53:06Z"
    - latency: 1.79358ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:52:06Z"
    - latency: 1.746158ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:51:06Z"
    - latency: 1.803048ms
      message: 'network-check-target-ip-10-0-136-251: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:50:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T22:17:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-127-to-network-check-target-ip-10-0-143-205
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-127.ec2.internal
      uid: abb0a167-1e61-4526-84ad-048505f99241
    resourceVersion: "59765"
    uid: 2c157bb8-aa4a-4c82-8e6e-1937964a0eae
  spec:
    sourcePod: network-check-source-989f8b8dc-phfph
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T22:24:06Z"
      message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.182221ms
      message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:59:06Z"
    - latency: 1.921256ms
      message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:58:06Z"
    - latency: 2.130542ms
      message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:57:06Z"
    - latency: 2.181608ms
      message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:56:06Z"
    - latency: 2.156267ms
      message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:55:06Z"
    - latency: 2.095143ms
      message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:54:06Z"
    - latency: 2.250154ms
      message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:53:06Z"
    - latency: 2.115611ms
      message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:52:06Z"
    - latency: 2.214061ms
      message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:51:06Z"
    - latency: 2.147049ms
      message: 'network-check-target-ip-10-0-143-205: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:50:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T22:17:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-127-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-127.ec2.internal
      uid: abb0a167-1e61-4526-84ad-048505f99241
    resourceVersion: "59766"
    uid: d6cb2e1c-ae7a-462b-8854-8c68f4a0fb06
  spec:
    sourcePod: network-check-source-989f8b8dc-phfph
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T22:23:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.128549ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:59:06Z"
    - latency: 1.871887ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:59:06Z"
    - latency: 777.348µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:58:06Z"
    - latency: 1.677622ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:58:06Z"
    - latency: 981.265µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:57:06Z"
    - latency: 1.984787ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:57:06Z"
    - latency: 1.139601ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:56:06Z"
    - latency: 1.753218ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:56:06Z"
    - latency: 984.486µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T22:55:06Z"
    - latency: 1.72795ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T22:55:06Z"
kind: List
metadata:
  resourceVersion: ""