apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:05:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-82-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-82.ec2.internal
      uid: 6770a2d8-8298-48da-a5bf-16ff3c8aa458
    resourceVersion: "27316"
    uid: f245076c-ac32-41d5-9949-b282e62aa362
  spec:
    sourcePod: network-check-source-6f78d59f99-jwhg9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:12:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.082065ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:54:43Z"
    - latency: 1.00239ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:53:43Z"
    - latency: 1.079226ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:52:43Z"
    - latency: 1.099278ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:51:43Z"
    - latency: 1.01876ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:50:43Z"
    - latency: 1.044265ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:49:43Z"
    - latency: 1.04169ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:48:43Z"
    - latency: 1.328255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:47:43Z"
    - latency: 971.489µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:46:43Z"
    - latency: 880.175µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:45:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:05:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-82-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-82.ec2.internal
      uid: 6770a2d8-8298-48da-a5bf-16ff3c8aa458
    resourceVersion: "26523"
    uid: a530f541-c803-4207-a1a0-c7c007a6c68d
  spec:
    sourcePod: network-check-source-6f78d59f99-jwhg9
    targetEndpoint: a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:11:43Z"
      message: 'load-balancer-api-external: tcp connection to a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.677404ms
      message: 'load-balancer-api-external: tcp connection to a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:53:43Z"
    - latency: 9.042596ms
      message: 'load-balancer-api-external: resolved host name a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:53:43Z"
    - latency: 15.012395ms
      message: 'load-balancer-api-external: tcp connection to a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:52:43Z"
    - latency: 8.627958ms
      message: 'load-balancer-api-external: resolved host name a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:52:43Z"
    - latency: 15.127408ms
      message: 'load-balancer-api-external: tcp connection to a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:51:43Z"
    - latency: 8.997198ms
      message: 'load-balancer-api-external: resolved host name a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:51:43Z"
    - latency: 16.24608ms
      message: 'load-balancer-api-external: tcp connection to a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:50:43Z"
    - latency: 8.95376ms
      message: 'load-balancer-api-external: resolved host name a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:50:43Z"
    - latency: 18.171686ms
      message: 'load-balancer-api-external: tcp connection to a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:49:43Z"
    - latency: 12.868225ms
      message: 'load-balancer-api-external: resolved host name a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:49:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:05:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-82-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-82.ec2.internal
      uid: 6770a2d8-8298-48da-a5bf-16ff3c8aa458
    resourceVersion: "26522"
    uid: bf5a90d8-98ea-4150-9635-75d20802796d
  spec:
    sourcePod: network-check-source-6f78d59f99-jwhg9
    targetEndpoint: a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:11:43Z"
      message: 'load-balancer-api-internal: tcp connection to a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.147346ms
      message: 'load-balancer-api-internal: tcp connection to a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:53:43Z"
    - latency: 8.969838ms
      message: 'load-balancer-api-internal: resolved host name a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:53:43Z"
    - latency: 18.852903ms
      message: 'load-balancer-api-internal: tcp connection to a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:52:43Z"
    - latency: 8.558537ms
      message: 'load-balancer-api-internal: resolved host name a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:52:43Z"
    - latency: 17.982887ms
      message: 'load-balancer-api-internal: tcp connection to a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:51:43Z"
    - latency: 8.915185ms
      message: 'load-balancer-api-internal: resolved host name a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:51:43Z"
    - latency: 16.318322ms
      message: 'load-balancer-api-internal: tcp connection to a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:50:43Z"
    - latency: 8.900697ms
      message: 'load-balancer-api-internal: resolved host name a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:50:43Z"
    - latency: 18.204765ms
      message: 'load-balancer-api-internal: tcp connection to a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:49:43Z"
    - latency: 12.756851ms
      message: 'load-balancer-api-internal: resolved host name a438b75f3365b41b59bb5f7e32e5bc5d-f5afba8503ad3519.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:49:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:05:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-82-to-network-check-target-ip-10-0-132-171
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-82.ec2.internal
      uid: 6770a2d8-8298-48da-a5bf-16ff3c8aa458
    resourceVersion: "27315"
    uid: 1301b7d3-7b7b-4b7e-9d41-4e702bbdc15a
  spec:
    sourcePod: network-check-source-6f78d59f99-jwhg9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:12:43Z"
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.468894ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:54:43Z"
    - latency: 2.303293ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:53:43Z"
    - latency: 2.276563ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:52:43Z"
    - latency: 2.513365ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:51:43Z"
    - latency: 2.415882ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:50:43Z"
    - latency: 2.533673ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:49:43Z"
    - latency: 2.625738ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:48:43Z"
    - latency: 2.147ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:47:43Z"
    - latency: 2.603203ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:46:43Z"
    - latency: 2.174439ms
      message: 'network-check-target-ip-10-0-132-171: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:45:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:05:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-82-to-network-check-target-ip-10-0-138-82
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-82.ec2.internal
      uid: 6770a2d8-8298-48da-a5bf-16ff3c8aa458
    resourceVersion: "27313"
    uid: 783c63ff-a698-4a9b-89df-a3c6c56a0c87
  spec:
    sourcePod: network-check-source-6f78d59f99-jwhg9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:12:43Z"
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.370037ms
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:54:43Z"
    - latency: 923.299µs
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:53:43Z"
    - latency: 718.087µs
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:52:43Z"
    - latency: 869.129µs
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:51:43Z"
    - latency: 785.71µs
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:50:43Z"
    - latency: 1.144692ms
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:49:43Z"
    - latency: 977.216µs
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:48:43Z"
    - latency: 875.616µs
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:47:43Z"
    - latency: 944.455µs
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:46:43Z"
    - latency: 839.921µs
      message: 'network-check-target-ip-10-0-138-82: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:45:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:05:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-82-to-network-check-target-ip-10-0-140-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-82.ec2.internal
      uid: 6770a2d8-8298-48da-a5bf-16ff3c8aa458
    resourceVersion: "27314"
    uid: 4eeffac0-9540-4747-89c2-3b570a87f72d
  spec:
    sourcePod: network-check-source-6f78d59f99-jwhg9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:12:43Z"
      message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.233243ms
      message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:54:43Z"
    - latency: 2.237636ms
      message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:53:43Z"
    - latency: 1.538673ms
      message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:52:43Z"
    - latency: 2.381623ms
      message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:51:43Z"
    - latency: 2.33087ms
      message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:50:43Z"
    - latency: 2.201682ms
      message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:49:43Z"
    - latency: 2.29295ms
      message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:48:43Z"
    - latency: 2.058439ms
      message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:47:43Z"
    - latency: 2.207442ms
      message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:46:43Z"
    - latency: 2.173503ms
      message: 'network-check-target-ip-10-0-140-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:45:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T03:05:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-82-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-82.ec2.internal
      uid: 6770a2d8-8298-48da-a5bf-16ff3c8aa458
    resourceVersion: "26521"
    uid: bdd3e9d9-2448-4236-b46b-5907d419ef02
  spec:
    sourcePod: network-check-source-6f78d59f99-jwhg9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T03:11:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 947.955µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:53:43Z"
    - latency: 2.049942ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:53:43Z"
    - latency: 1.019791ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:52:43Z"
    - latency: 1.899617ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:52:43Z"
    - latency: 1.227634ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:51:43Z"
    - latency: 1.860962ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:51:43Z"
    - latency: 867.736µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:50:43Z"
    - latency: 1.820787ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:50:43Z"
    - latency: 1.091538ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T03:49:43Z"
    - latency: 2.486814ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T03:49:43Z"
kind: List
metadata:
  resourceVersion: ""