apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:26:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-131-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-131.ec2.internal
      uid: 29c4a802-c10b-466f-be38-aec4941d7755
    resourceVersion: "59882"
    uid: c0382d2a-188a-4b92-81ed-45c058a7266e
  spec:
    sourcePod: network-check-source-869dcfcdcd-nst9b
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:33:54Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.134252ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:08:54Z"
    - latency: 1.605025ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:07:54Z"
    - latency: 950.26µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:06:54Z"
    - latency: 1.20375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:05:54Z"
    - latency: 888.974µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:04:54Z"
    - latency: 1.003559ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:03:54Z"
    - latency: 1.151027ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:02:54Z"
    - latency: 1.072188ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:01:54Z"
    - latency: 1.413516ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:00:54Z"
    - latency: 1.566038ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:59:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:26:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-131-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-131.ec2.internal
      uid: 29c4a802-c10b-466f-be38-aec4941d7755
    resourceVersion: "59885"
    uid: a0de8c78-6583-4913-9c02-01caaa0c0f5c
  spec:
    sourcePod: network-check-source-869dcfcdcd-nst9b
    targetEndpoint: aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:32:54Z"
      message: 'load-balancer-api-external: tcp connection to aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.469748ms
      message: 'load-balancer-api-external: tcp connection to aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:08:54Z"
    - latency: 7.485905ms
      message: 'load-balancer-api-external: resolved host name aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:08:54Z"
    - latency: 6.013102ms
      message: 'load-balancer-api-external: tcp connection to aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:07:54Z"
    - latency: 7.176187ms
      message: 'load-balancer-api-external: resolved host name aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:07:54Z"
    - latency: 5.893616ms
      message: 'load-balancer-api-external: tcp connection to aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:06:54Z"
    - latency: 11.060807ms
      message: 'load-balancer-api-external: resolved host name aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:06:54Z"
    - latency: 4.195274ms
      message: 'load-balancer-api-external: tcp connection to aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:05:54Z"
    - latency: 7.790277ms
      message: 'load-balancer-api-external: resolved host name aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:05:54Z"
    - latency: 6.86018ms
      message: 'load-balancer-api-external: tcp connection to aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:04:54Z"
    - latency: 7.766828ms
      message: 'load-balancer-api-external: resolved host name aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:04:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:26:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-131-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-131.ec2.internal
      uid: 29c4a802-c10b-466f-be38-aec4941d7755
    resourceVersion: "59884"
    uid: 34617e4d-5ee0-44df-b5dd-a6cd433e3eb7
  spec:
    sourcePod: network-check-source-869dcfcdcd-nst9b
    targetEndpoint: aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:32:54Z"
      message: 'load-balancer-api-internal: tcp connection to aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.411352ms
      message: 'load-balancer-api-internal: tcp connection to aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:08:54Z"
    - latency: 7.521434ms
      message: 'load-balancer-api-internal: resolved host name aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:08:54Z"
    - latency: 6.045131ms
      message: 'load-balancer-api-internal: tcp connection to aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:07:54Z"
    - latency: 7.061962ms
      message: 'load-balancer-api-internal: resolved host name aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:07:54Z"
    - latency: 5.770466ms
      message: 'load-balancer-api-internal: tcp connection to aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:06:54Z"
    - latency: 11.128166ms
      message: 'load-balancer-api-internal: resolved host name aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:06:54Z"
    - latency: 5.371205ms
      message: 'load-balancer-api-internal: tcp connection to aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:05:54Z"
    - latency: 7.741133ms
      message: 'load-balancer-api-internal: resolved host name aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:05:54Z"
    - latency: 6.844277ms
      message: 'load-balancer-api-internal: tcp connection to aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:04:54Z"
    - latency: 7.675401ms
      message: 'load-balancer-api-internal: resolved host name aceb501ce6ae2478c91c8445ceea3d1a-d55f67cab2405b65.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:04:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:26:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-131-to-network-check-target-ip-10-0-128-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-131.ec2.internal
      uid: 29c4a802-c10b-466f-be38-aec4941d7755
    resourceVersion: "59879"
    uid: f37282d2-9f6c-44e9-a8d8-afdcb1c53808
  spec:
    sourcePod: network-check-source-869dcfcdcd-nst9b
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:33:54Z"
      message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.343725ms
      message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:08:54Z"
    - latency: 2.471722ms
      message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:07:54Z"
    - latency: 2.263499ms
      message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:06:54Z"
    - latency: 2.108115ms
      message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:05:54Z"
    - latency: 1.990717ms
      message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:04:54Z"
    - latency: 2.268596ms
      message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:03:54Z"
    - latency: 2.44779ms
      message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:02:54Z"
    - latency: 2.75403ms
      message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:01:54Z"
    - latency: 2.533541ms
      message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:00:54Z"
    - latency: 1.963014ms
      message: 'network-check-target-ip-10-0-128-235: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:59:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:26:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-131-to-network-check-target-ip-10-0-138-184
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-131.ec2.internal
      uid: 29c4a802-c10b-466f-be38-aec4941d7755
    resourceVersion: "59880"
    uid: eb91946f-e5c2-4145-806a-c217f9d4ab8d
  spec:
    sourcePod: network-check-source-869dcfcdcd-nst9b
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:33:54Z"
      message: 'network-check-target-ip-10-0-138-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.238604ms
      message: 'network-check-target-ip-10-0-138-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:08:54Z"
    - latency: 2.214779ms
      message: 'network-check-target-ip-10-0-138-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:07:54Z"
    - latency: 2.124967ms
      message: 'network-check-target-ip-10-0-138-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:06:54Z"
    - latency: 2.300191ms
      message: 'network-check-target-ip-10-0-138-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:05:54Z"
    - latency: 2.469769ms
      message: 'network-check-target-ip-10-0-138-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:04:54Z"
    - latency: 2.394325ms
      message: 'network-check-target-ip-10-0-138-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:03:54Z"
    - latency: 2.272344ms
      message: 'network-check-target-ip-10-0-138-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:02:54Z"
    - latency: 2.47018ms
      message: 'network-check-target-ip-10-0-138-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:01:54Z"
    - latency: 2.496707ms
      message: 'network-check-target-ip-10-0-138-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:00:54Z"
    - latency: 1.986584ms
      message: 'network-check-target-ip-10-0-138-184: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:59:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:26:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-131-to-network-check-target-ip-10-0-142-131
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-131.ec2.internal
      uid: 29c4a802-c10b-466f-be38-aec4941d7755
    resourceVersion: "59878"
    uid: 0b0a0627-2933-4f9f-a572-293d4af649cd
  spec:
    sourcePod: network-check-source-869dcfcdcd-nst9b
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:33:54Z"
      message: 'network-check-target-ip-10-0-142-131: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 882.688µs
      message: 'network-check-target-ip-10-0-142-131: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:08:54Z"
    - latency: 938.507µs
      message: 'network-check-target-ip-10-0-142-131: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:07:54Z"
    - latency: 1.168087ms
      message: 'network-check-target-ip-10-0-142-131: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:06:54Z"
    - latency: 1.370971ms
      message: 'network-check-target-ip-10-0-142-131: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:05:54Z"
    - latency: 992.877µs
      message: 'network-check-target-ip-10-0-142-131: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:04:54Z"
    - latency: 1.131351ms
      message: 'network-check-target-ip-10-0-142-131: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:03:54Z"
    - latency: 1.397241ms
      message: 'network-check-target-ip-10-0-142-131: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:02:54Z"
    - latency: 1.190845ms
      message: 'network-check-target-ip-10-0-142-131: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:01:54Z"
    - latency: 1.025754ms
      message: 'network-check-target-ip-10-0-142-131: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:00:54Z"
    - latency: 825.978µs
      message: 'network-check-target-ip-10-0-142-131: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T12:59:54Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T12:26:53Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-131-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-131.ec2.internal
      uid: 29c4a802-c10b-466f-be38-aec4941d7755
    resourceVersion: "59881"
    uid: 8d5ad7d3-d20b-4b76-92d1-82c250a5adeb
  spec:
    sourcePod: network-check-source-869dcfcdcd-nst9b
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T12:32:54Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.276667ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:08:54Z"
    - latency: 1.918156ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:08:54Z"
    - latency: 1.022271ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:07:54Z"
    - latency: 2.058739ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:07:54Z"
    - latency: 1.075417ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:06:54Z"
    - latency: 2.061891ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:06:54Z"
    - latency: 922.654µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:05:54Z"
    - latency: 2.03444ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:05:54Z"
    - latency: 1.231459ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T13:04:54Z"
    - latency: 1.884726ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T13:04:54Z"
kind: List
metadata:
  resourceVersion: ""