apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:32:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-132-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-132.ec2.internal
      uid: ce98d3b9-d1ac-4bd5-965b-8d7bc0678fc7
    resourceVersion: "71890"
    uid: a3151905-9bd3-415f-9f75-bffdb1e399b8
  spec:
    sourcePod: network-check-source-7cbc45fddc-vsp4l
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:39:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.06515ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:35:44Z"
    - latency: 968.282µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:34:44Z"
    - latency: 1.122175ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:33:44Z"
    - latency: 1.418155ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:32:44Z"
    - latency: 1.380353ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:31:44Z"
    - latency: 939.502µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:30:44Z"
    - latency: 879.465µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:29:44Z"
    - latency: 958.261µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:28:44Z"
    - latency: 1.087406ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:27:44Z"
    - latency: 1.175264ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:26:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:32:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-132-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-132.ec2.internal
      uid: ce98d3b9-d1ac-4bd5-965b-8d7bc0678fc7
    resourceVersion: "69517"
    uid: ed3deb90-acea-440c-8342-3606e039f3a5
  spec:
    sourcePod: network-check-source-7cbc45fddc-vsp4l
    targetEndpoint: adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:38:44Z"
      message: 'load-balancer-api-external: tcp connection to adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.766766ms
      message: 'load-balancer-api-external: tcp connection to adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:32:44Z"
    - latency: 7.017018ms
      message: 'load-balancer-api-external: resolved host name adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:32:44Z"
    - latency: 5.721156ms
      message: 'load-balancer-api-external: tcp connection to adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:31:44Z"
    - latency: 8.399695ms
      message: 'load-balancer-api-external: resolved host name adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:31:44Z"
    - latency: 4.472388ms
      message: 'load-balancer-api-external: tcp connection to adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:30:44Z"
    - latency: 9.51214ms
      message: 'load-balancer-api-external: resolved host name adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:30:44Z"
    - latency: 5.505139ms
      message: 'load-balancer-api-external: tcp connection to adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:29:44Z"
    - latency: 8.283588ms
      message: 'load-balancer-api-external: resolved host name adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:29:44Z"
    - latency: 4.984998ms
      message: 'load-balancer-api-external: tcp connection to adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:28:44Z"
    - latency: 8.57519ms
      message: 'load-balancer-api-external: resolved host name adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:28:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:32:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-132-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-132.ec2.internal
      uid: ce98d3b9-d1ac-4bd5-965b-8d7bc0678fc7
    resourceVersion: "69516"
    uid: f2102e27-176b-4dc5-b89c-cb05aba607b4
  spec:
    sourcePod: network-check-source-7cbc45fddc-vsp4l
    targetEndpoint: adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:38:44Z"
      message: 'load-balancer-api-internal: tcp connection to adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.721132ms
      message: 'load-balancer-api-internal: tcp connection to adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:32:44Z"
    - latency: 6.991909ms
      message: 'load-balancer-api-internal: resolved host name adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:32:44Z"
    - latency: 6.716537ms
      message: 'load-balancer-api-internal: tcp connection to adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:31:44Z"
    - latency: 8.317107ms
      message: 'load-balancer-api-internal: resolved host name adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:31:44Z"
    - latency: 4.453749ms
      message: 'load-balancer-api-internal: tcp connection to adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:30:44Z"
    - latency: 9.479107ms
      message: 'load-balancer-api-internal: resolved host name adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:30:44Z"
    - latency: 4.896594ms
      message: 'load-balancer-api-internal: tcp connection to adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:29:44Z"
    - latency: 8.274003ms
      message: 'load-balancer-api-internal: resolved host name adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:29:44Z"
    - latency: 5.083293ms
      message: 'load-balancer-api-internal: tcp connection to adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:28:44Z"
    - latency: 8.46409ms
      message: 'load-balancer-api-internal: resolved host name adfef2d5d73c949d8be48457b1268d53-7aa65380b81c4a0f.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:28:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:32:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-132-to-network-check-target-ip-10-0-136-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-132.ec2.internal
      uid: ce98d3b9-d1ac-4bd5-965b-8d7bc0678fc7
    resourceVersion: "71889"
    uid: c1318b4e-d5cd-43c3-b1c9-ba952e8bd12b
  spec:
    sourcePod: network-check-source-7cbc45fddc-vsp4l
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:39:44Z"
      message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.351975ms
      message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:35:44Z"
    - latency: 1.372998ms
      message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:34:44Z"
    - latency: 1.03189ms
      message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:33:44Z"
    - latency: 1.003383ms
      message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:32:44Z"
    - latency: 1.576126ms
      message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:31:44Z"
    - latency: 1.522282ms
      message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:30:44Z"
    - latency: 867.802µs
      message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:29:44Z"
    - latency: 922.868µs
      message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:28:44Z"
    - latency: 1.304002ms
      message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:27:44Z"
    - latency: 951.291µs
      message: 'network-check-target-ip-10-0-136-132: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:26:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:32:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-132-to-network-check-target-ip-10-0-138-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-132.ec2.internal
      uid: ce98d3b9-d1ac-4bd5-965b-8d7bc0678fc7
    resourceVersion: "71888"
    uid: 80b637eb-baeb-43ca-8d39-1f9091aa87c7
  spec:
    sourcePod: network-check-source-7cbc45fddc-vsp4l
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:39:44Z"
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.263472ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:35:44Z"
    - latency: 2.218166ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:34:44Z"
    - latency: 2.254943ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:33:44Z"
    - latency: 2.391915ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:32:44Z"
    - latency: 2.178398ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:31:44Z"
    - latency: 2.401805ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:30:44Z"
    - latency: 2.102906ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:29:44Z"
    - latency: 2.475068ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:28:44Z"
    - latency: 2.373059ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:27:44Z"
    - latency: 2.205254ms
      message: 'network-check-target-ip-10-0-138-98: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:26:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:32:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-132-to-network-check-target-ip-10-0-139-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-132.ec2.internal
      uid: ce98d3b9-d1ac-4bd5-965b-8d7bc0678fc7
    resourceVersion: "71887"
    uid: de1825f6-f5bf-4c56-8df8-14f4bd366f5b
  spec:
    sourcePod: network-check-source-7cbc45fddc-vsp4l
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:39:44Z"
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.090728ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:35:44Z"
    - latency: 2.618737ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:34:44Z"
    - latency: 2.132008ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:33:44Z"
    - latency: 2.349922ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:32:44Z"
    - latency: 2.193693ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:31:44Z"
    - latency: 2.262423ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:30:44Z"
    - latency: 2.009384ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:29:44Z"
    - latency: 2.893072ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:28:44Z"
    - latency: 1.95746ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:27:44Z"
    - latency: 2.545534ms
      message: 'network-check-target-ip-10-0-139-75: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:26:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T18:32:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-132-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-132.ec2.internal
      uid: ce98d3b9-d1ac-4bd5-965b-8d7bc0678fc7
    resourceVersion: "69515"
    uid: b8b74f50-77ea-4c4d-81c2-ac886db0ed88
  spec:
    sourcePod: network-check-source-7cbc45fddc-vsp4l
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T18:38:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.111576ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:32:44Z"
    - latency: 1.804538ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:32:44Z"
    - latency: 909.18µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:31:44Z"
    - latency: 2.276004ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:31:44Z"
    - latency: 839.769µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:30:44Z"
    - latency: 1.800014ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:30:44Z"
    - latency: 831.303µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:29:44Z"
    - latency: 1.692445ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:29:44Z"
    - latency: 1.239851ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T19:28:44Z"
    - latency: 1.913618ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T19:28:44Z"
kind: List
metadata:
  resourceVersion: ""