apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:07:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-197-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-197.ec2.internal
      uid: 9fd8570f-b9d7-43ae-ac9a-0f197f034d5c
    resourceVersion: "53420"
    uid: a67a1438-d184-420f-a504-3dbc5947dadb
  spec:
    sourcePod: network-check-source-989f8b8dc-lgkg7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:15:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 863.42µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:43:00Z"
    - latency: 1.323647ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:42:00Z"
    - latency: 1.07169ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:41:00Z"
    - latency: 923.128µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:40:00Z"
    - latency: 1.0956ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:39:00Z"
    - latency: 1.015832ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:38:00Z"
    - latency: 1.022418ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:37:00Z"
    - latency: 1.013833ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:36:00Z"
    - latency: 905.507µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:35:00Z"
    - latency: 837.917µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:34:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:07:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-197-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-197.ec2.internal
      uid: 9fd8570f-b9d7-43ae-ac9a-0f197f034d5c
    resourceVersion: "54484"
    uid: fa784e08-8d00-4e3e-bd9f-08f52798f871
  spec:
    sourcePod: network-check-source-989f8b8dc-lgkg7
    targetEndpoint: abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:14:00Z"
      message: 'load-balancer-api-external: tcp connection to abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.838469ms
      message: 'load-balancer-api-external: tcp connection to abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:44:00Z"
    - latency: 6.916315ms
      message: 'load-balancer-api-external: resolved host name abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:44:00Z"
    - latency: 4.190278ms
      message: 'load-balancer-api-external: tcp connection to abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:43:00Z"
    - latency: 5.848405ms
      message: 'load-balancer-api-external: resolved host name abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:43:00Z"
    - latency: 4.488659ms
      message: 'load-balancer-api-external: tcp connection to abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:42:00Z"
    - latency: 7.95092ms
      message: 'load-balancer-api-external: resolved host name abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:42:00Z"
    - latency: 4.710578ms
      message: 'load-balancer-api-external: tcp connection to abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:41:00Z"
    - latency: 6.89649ms
      message: 'load-balancer-api-external: resolved host name abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:41:00Z"
    - latency: 4.171314ms
      message: 'load-balancer-api-external: tcp connection to abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:40:00Z"
    - latency: 7.131567ms
      message: 'load-balancer-api-external: resolved host name abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:40:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:07:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-197-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-197.ec2.internal
      uid: 9fd8570f-b9d7-43ae-ac9a-0f197f034d5c
    resourceVersion: "54483"
    uid: 3139d82a-0cd9-4ad6-b133-49cd482fc3c5
  spec:
    sourcePod: network-check-source-989f8b8dc-lgkg7
    targetEndpoint: abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:14:00Z"
      message: 'load-balancer-api-internal: tcp connection to abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.880789ms
      message: 'load-balancer-api-internal: tcp connection to abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:44:00Z"
    - latency: 6.836164ms
      message: 'load-balancer-api-internal: resolved host name abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:44:00Z"
    - latency: 3.900022ms
      message: 'load-balancer-api-internal: tcp connection to abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:43:00Z"
    - latency: 5.869589ms
      message: 'load-balancer-api-internal: resolved host name abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:43:00Z"
    - latency: 4.748536ms
      message: 'load-balancer-api-internal: tcp connection to abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:42:00Z"
    - latency: 7.868313ms
      message: 'load-balancer-api-internal: resolved host name abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:42:00Z"
    - latency: 5.566921ms
      message: 'load-balancer-api-internal: tcp connection to abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:41:00Z"
    - latency: 6.99829ms
      message: 'load-balancer-api-internal: resolved host name abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:41:00Z"
    - latency: 4.174413ms
      message: 'load-balancer-api-internal: tcp connection to abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:40:00Z"
    - latency: 7.028813ms
      message: 'load-balancer-api-internal: resolved host name abac41fac8dfe4bc384d57112569bd62-dbf2ae49fac6095f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:40:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:07:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-197-to-network-check-target-ip-10-0-129-175
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-197.ec2.internal
      uid: 9fd8570f-b9d7-43ae-ac9a-0f197f034d5c
    resourceVersion: "53415"
    uid: 76e4f946-915e-4815-8f65-e220a2248e1b
  spec:
    sourcePod: network-check-source-989f8b8dc-lgkg7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:15:00Z"
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.489965ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:43:00Z"
    - latency: 2.397897ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:42:00Z"
    - latency: 2.337375ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:41:00Z"
    - latency: 2.200509ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:40:00Z"
    - latency: 2.463345ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:39:00Z"
    - latency: 2.09316ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:38:00Z"
    - latency: 2.548392ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:37:00Z"
    - latency: 2.406655ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:36:00Z"
    - latency: 2.130669ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:35:00Z"
    - latency: 2.180454ms
      message: 'network-check-target-ip-10-0-129-175: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:34:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:07:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-197-to-network-check-target-ip-10-0-131-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-197.ec2.internal
      uid: 9fd8570f-b9d7-43ae-ac9a-0f197f034d5c
    resourceVersion: "53416"
    uid: 6a67e66e-1e1c-4643-97df-cf8d031cf1a8
  spec:
    sourcePod: network-check-source-989f8b8dc-lgkg7
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:15:00Z"
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.314631ms
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:43:00Z"
    - latency: 1.102379ms
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:42:00Z"
    - latency: 1.222198ms
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:41:00Z"
    - latency: 908.36µs
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:40:00Z"
    - latency: 947.896µs
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:39:00Z"
    - latency: 1.165838ms
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:38:00Z"
    - latency: 956.724µs
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:37:00Z"
    - latency: 1.033792ms
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:36:00Z"
    - latency: 780.773µs
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:35:00Z"
    - latency: 1.03481ms
      message: 'network-check-target-ip-10-0-131-197: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:34:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:07:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-197-to-network-check-target-ip-10-0-138-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-197.ec2.internal
      uid: 9fd8570f-b9d7-43ae-ac9a-0f197f034d5c
    resourceVersion: "53418"
    uid: 44680418-dbe5-4291-bf76-dd8e27e1ee9e
  spec:
    sourcePod: network-check-source-989f8b8dc-lgkg7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:15:00Z"
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.89569ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:43:00Z"
    - latency: 2.509742ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:42:00Z"
    - latency: 2.306519ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:41:00Z"
    - latency: 2.626886ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:40:00Z"
    - latency: 2.397318ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:39:00Z"
    - latency: 2.244001ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:38:00Z"
    - latency: 2.395052ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:37:00Z"
    - latency: 2.222463ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:36:00Z"
    - latency: 2.100406ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:35:00Z"
    - latency: 2.045451ms
      message: 'network-check-target-ip-10-0-138-36: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:34:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T12:07:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-197-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-197.ec2.internal
      uid: 9fd8570f-b9d7-43ae-ac9a-0f197f034d5c
    resourceVersion: "54482"
    uid: 69f138ef-c16f-4b70-8584-ccc56a9b0474
  spec:
    sourcePod: network-check-source-989f8b8dc-lgkg7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T12:14:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.045761ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:44:00Z"
    - latency: 1.663343ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:44:00Z"
    - latency: 810.634µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:43:00Z"
    - latency: 1.509512ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:43:00Z"
    - latency: 1.123639ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:42:00Z"
    - latency: 1.819047ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:42:00Z"
    - latency: 829.278µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:41:00Z"
    - latency: 1.968653ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:41:00Z"
    - latency: 930.664µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T12:40:00Z"
    - latency: 2.080343ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T12:40:00Z"
kind: List
metadata:
  resourceVersion: ""