apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T23:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-128-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-128.ec2.internal
      uid: 043bec0d-af02-4b4d-99dc-ca2d948d964f
    resourceVersion: "55690"
    uid: 9c5fe45b-511e-4da7-9c3c-2d3b43b17734
  spec:
    sourcePod: network-check-source-869dcfcdcd-h5kbv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T23:37:50Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 914.228µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:05:50Z"
    - latency: 1.325242ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:04:50Z"
    - latency: 1.123346ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:03:50Z"
    - latency: 1.227492ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:02:50Z"
    - latency: 1.339325ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:01:50Z"
    - latency: 1.400531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:00:50Z"
    - latency: 1.50768ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:59:50Z"
    - latency: 1.155622ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:58:50Z"
    - latency: 1.219094ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:57:50Z"
    - latency: 1.268206ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:56:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T23:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-128-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-128.ec2.internal
      uid: 043bec0d-af02-4b4d-99dc-ca2d948d964f
    resourceVersion: "56668"
    uid: f2e4415f-1768-40b6-bd02-322f64182aad
  spec:
    sourcePod: network-check-source-869dcfcdcd-h5kbv
    targetEndpoint: aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T23:36:50Z"
      message: 'load-balancer-api-external: tcp connection to aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.68023ms
      message: 'load-balancer-api-external: tcp connection to aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:06:50Z"
    - latency: 7.528825ms
      message: 'load-balancer-api-external: resolved host name aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:06:50Z"
    - latency: 4.613245ms
      message: 'load-balancer-api-external: tcp connection to aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:05:50Z"
    - latency: 8.206647ms
      message: 'load-balancer-api-external: resolved host name aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:05:50Z"
    - latency: 5.700989ms
      message: 'load-balancer-api-external: tcp connection to aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:04:50Z"
    - latency: 8.606656ms
      message: 'load-balancer-api-external: resolved host name aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:04:50Z"
    - latency: 4.462761ms
      message: 'load-balancer-api-external: tcp connection to aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:03:50Z"
    - latency: 7.583429ms
      message: 'load-balancer-api-external: resolved host name aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:03:50Z"
    - latency: 3.59432ms
      message: 'load-balancer-api-external: tcp connection to aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:02:50Z"
    - latency: 6.69873ms
      message: 'load-balancer-api-external: resolved host name aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:02:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T23:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-128-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-128.ec2.internal
      uid: 043bec0d-af02-4b4d-99dc-ca2d948d964f
    resourceVersion: "56667"
    uid: eeaad00a-df44-4212-a366-34259ebd12f1
  spec:
    sourcePod: network-check-source-869dcfcdcd-h5kbv
    targetEndpoint: aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T23:36:50Z"
      message: 'load-balancer-api-internal: tcp connection to aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.708833ms
      message: 'load-balancer-api-internal: tcp connection to aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:06:50Z"
    - latency: 7.87585ms
      message: 'load-balancer-api-internal: resolved host name aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:06:50Z"
    - latency: 4.628413ms
      message: 'load-balancer-api-internal: tcp connection to aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:05:50Z"
    - latency: 8.17134ms
      message: 'load-balancer-api-internal: resolved host name aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:05:50Z"
    - latency: 5.658959ms
      message: 'load-balancer-api-internal: tcp connection to aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:04:50Z"
    - latency: 8.647491ms
      message: 'load-balancer-api-internal: resolved host name aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:04:50Z"
    - latency: 4.037541ms
      message: 'load-balancer-api-internal: tcp connection to aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:03:50Z"
    - latency: 7.506024ms
      message: 'load-balancer-api-internal: resolved host name aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:03:50Z"
    - latency: 5.854167ms
      message: 'load-balancer-api-internal: tcp connection to aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:02:50Z"
    - latency: 6.667015ms
      message: 'load-balancer-api-internal: resolved host name aae9f6531bc22442989ea485541da23e-d2fa091a507b523e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:02:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T23:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-128-to-network-check-target-ip-10-0-132-128
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-128.ec2.internal
      uid: 043bec0d-af02-4b4d-99dc-ca2d948d964f
    resourceVersion: "55687"
    uid: ff5f3e8c-e614-4d0e-98d6-710c08068c00
  spec:
    sourcePod: network-check-source-869dcfcdcd-h5kbv
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T23:37:50Z"
      message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 943.046µs
      message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:05:50Z"
    - latency: 1.049512ms
      message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:04:50Z"
    - latency: 1.431619ms
      message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:03:50Z"
    - latency: 892.478µs
      message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:02:50Z"
    - latency: 1.654383ms
      message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:01:50Z"
    - latency: 1.617617ms
      message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:00:50Z"
    - latency: 1.392323ms
      message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:59:50Z"
    - latency: 815.401µs
      message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:58:50Z"
    - latency: 826.235µs
      message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:57:50Z"
    - latency: 1.340547ms
      message: 'network-check-target-ip-10-0-132-128: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:56:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T23:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-128-to-network-check-target-ip-10-0-140-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-128.ec2.internal
      uid: 043bec0d-af02-4b4d-99dc-ca2d948d964f
    resourceVersion: "55688"
    uid: d5c5b75f-dfd5-4725-ae72-e27d1eb8ec02
  spec:
    sourcePod: network-check-source-869dcfcdcd-h5kbv
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T23:37:50Z"
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.103293ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:05:50Z"
    - latency: 2.324274ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:04:50Z"
    - latency: 2.456561ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:03:50Z"
    - latency: 2.32311ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:02:50Z"
    - latency: 2.538994ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:01:50Z"
    - latency: 2.435326ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:00:50Z"
    - latency: 2.489417ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:59:50Z"
    - latency: 2.258469ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:58:50Z"
    - latency: 2.331177ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:57:50Z"
    - latency: 2.032225ms
      message: 'network-check-target-ip-10-0-140-8: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:56:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T23:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-128-to-network-check-target-ip-10-0-143-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-128.ec2.internal
      uid: 043bec0d-af02-4b4d-99dc-ca2d948d964f
    resourceVersion: "55689"
    uid: 97ed1303-a409-4bab-a9b0-16af45882cb7
  spec:
    sourcePod: network-check-source-869dcfcdcd-h5kbv
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T23:37:50Z"
      message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.042025ms
      message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:05:50Z"
    - latency: 2.038386ms
      message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:04:50Z"
    - latency: 2.020778ms
      message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:03:50Z"
    - latency: 1.964789ms
      message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:02:50Z"
    - latency: 2.199456ms
      message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:01:50Z"
    - latency: 1.876429ms
      message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:00:50Z"
    - latency: 2.016084ms
      message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:59:50Z"
    - latency: 2.052356ms
      message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:58:50Z"
    - latency: 1.958001ms
      message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:57:50Z"
    - latency: 2.090119ms
      message: 'network-check-target-ip-10-0-143-88: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T23:56:50Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T23:30:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-128-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-128.ec2.internal
      uid: 043bec0d-af02-4b4d-99dc-ca2d948d964f
    resourceVersion: "56666"
    uid: 345d4d5e-be3b-44a8-b6bb-43fbf6a64376
  spec:
    sourcePod: network-check-source-869dcfcdcd-h5kbv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T23:36:50Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.00763ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:06:50Z"
    - latency: 2.875072ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:06:50Z"
    - latency: 877.659µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:05:50Z"
    - latency: 1.937917ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:05:50Z"
    - latency: 1.044845ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:04:50Z"
    - latency: 1.899676ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:04:50Z"
    - latency: 921.93µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:03:50Z"
    - latency: 1.608582ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:03:50Z"
    - latency: 944.847µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T00:02:50Z"
    - latency: 1.911992ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T00:02:50Z"
kind: List
metadata:
  resourceVersion: ""