apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T17:13:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-222-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-222.ec2.internal
      uid: 9af78ea6-d6eb-42e9-9c06-2d05ac659166
    resourceVersion: "159319"
    uid: a0ca4f68-39df-4223-b13e-727aba93940a
  spec:
    sourcePod: network-check-source-6f78d59f99-z6b8h
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T17:20:52Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 878.577µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:30:52Z"
    - latency: 818.991µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:29:52Z"
    - latency: 1.217371ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:28:52Z"
    - latency: 1.502652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:27:52Z"
    - latency: 957.944µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:26:52Z"
    - latency: 1.256528ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:25:52Z"
    - latency: 1.30906ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:24:52Z"
    - latency: 884.973µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:23:52Z"
    - latency: 986.308µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:22:52Z"
    - latency: 1.336316ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:21:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T17:13:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-222-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-222.ec2.internal
      uid: 9af78ea6-d6eb-42e9-9c06-2d05ac659166
    resourceVersion: "159899"
    uid: 2a7f68dc-3b62-4a65-8ce1-9365bdfd83c3
  spec:
    sourcePod: network-check-source-6f78d59f99-z6b8h
    targetEndpoint: aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T17:19:52Z"
      message: 'load-balancer-api-external: tcp connection to aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.224492ms
      message: 'load-balancer-api-external: tcp connection to aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:31:52Z"
    - latency: 6.977047ms
      message: 'load-balancer-api-external: resolved host name aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:31:52Z"
    - latency: 18.181937ms
      message: 'load-balancer-api-external: tcp connection to aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:30:52Z"
    - latency: 6.864094ms
      message: 'load-balancer-api-external: resolved host name aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:30:52Z"
    - latency: 17.216392ms
      message: 'load-balancer-api-external: tcp connection to aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:29:52Z"
    - latency: 6.957779ms
      message: 'load-balancer-api-external: resolved host name aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:29:52Z"
    - latency: 17.673013ms
      message: 'load-balancer-api-external: tcp connection to aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:28:52Z"
    - latency: 6.520234ms
      message: 'load-balancer-api-external: resolved host name aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:28:52Z"
    - latency: 18.515115ms
      message: 'load-balancer-api-external: tcp connection to aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:27:52Z"
    - latency: 6.904826ms
      message: 'load-balancer-api-external: resolved host name aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:27:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T17:13:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-222-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-222.ec2.internal
      uid: 9af78ea6-d6eb-42e9-9c06-2d05ac659166
    resourceVersion: "159900"
    uid: bfbea36d-d00c-4be3-9227-900ac971879d
  spec:
    sourcePod: network-check-source-6f78d59f99-z6b8h
    targetEndpoint: aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T17:19:52Z"
      message: 'load-balancer-api-internal: tcp connection to aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 27.01078ms
      message: 'load-balancer-api-internal: tcp connection to aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:31:52Z"
    - latency: 7.044653ms
      message: 'load-balancer-api-internal: resolved host name aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:31:52Z"
    - latency: 17.914518ms
      message: 'load-balancer-api-internal: tcp connection to aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:30:52Z"
    - latency: 6.922193ms
      message: 'load-balancer-api-internal: resolved host name aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:30:52Z"
    - latency: 17.327548ms
      message: 'load-balancer-api-internal: tcp connection to aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:29:52Z"
    - latency: 7.00966ms
      message: 'load-balancer-api-internal: resolved host name aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:29:52Z"
    - latency: 15.48688ms
      message: 'load-balancer-api-internal: tcp connection to aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:28:52Z"
    - latency: 6.576773ms
      message: 'load-balancer-api-internal: resolved host name aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:28:52Z"
    - latency: 18.529595ms
      message: 'load-balancer-api-internal: tcp connection to aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:27:52Z"
    - latency: 6.957536ms
      message: 'load-balancer-api-internal: resolved host name aff66a5d44d8949f29a5c1f6f666ea94-c872690aab2d5bef.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:27:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T17:13:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-222-to-network-check-target-ip-10-0-135-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-222.ec2.internal
      uid: 9af78ea6-d6eb-42e9-9c06-2d05ac659166
    resourceVersion: "159318"
    uid: 1c3f10d8-eb6d-4e1e-a867-cb9548c3b1ce
  spec:
    sourcePod: network-check-source-6f78d59f99-z6b8h
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T17:20:52Z"
      message: 'network-check-target-ip-10-0-135-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.436898ms
      message: 'network-check-target-ip-10-0-135-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:30:52Z"
    - latency: 2.229577ms
      message: 'network-check-target-ip-10-0-135-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:29:52Z"
    - latency: 2.458244ms
      message: 'network-check-target-ip-10-0-135-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:28:52Z"
    - latency: 2.440286ms
      message: 'network-check-target-ip-10-0-135-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:27:52Z"
    - latency: 2.490891ms
      message: 'network-check-target-ip-10-0-135-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:26:52Z"
    - latency: 2.54012ms
      message: 'network-check-target-ip-10-0-135-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:25:52Z"
    - latency: 2.32536ms
      message: 'network-check-target-ip-10-0-135-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:24:52Z"
    - latency: 2.108859ms
      message: 'network-check-target-ip-10-0-135-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:23:52Z"
    - latency: 2.257782ms
      message: 'network-check-target-ip-10-0-135-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:22:52Z"
    - latency: 8.535293ms
      message: 'network-check-target-ip-10-0-135-170: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:21:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T17:13:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-222-to-network-check-target-ip-10-0-139-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-222.ec2.internal
      uid: 9af78ea6-d6eb-42e9-9c06-2d05ac659166
    resourceVersion: "159316"
    uid: 368c2803-6e68-4d3c-acc2-34c7eb7a6cfb
  spec:
    sourcePod: network-check-source-6f78d59f99-z6b8h
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T17:20:52Z"
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 885.389µs
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:30:52Z"
    - latency: 798.155µs
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:29:52Z"
    - latency: 928.655µs
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:28:52Z"
    - latency: 1.805242ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:27:52Z"
    - latency: 1.265933ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:26:52Z"
    - latency: 1.026138ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:25:52Z"
    - latency: 1.035954ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:24:52Z"
    - latency: 1.326872ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:23:52Z"
    - latency: 960.329µs
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:22:52Z"
    - latency: 2.983294ms
      message: 'network-check-target-ip-10-0-139-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:21:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T17:13:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-222-to-network-check-target-ip-10-0-143-147
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-222.ec2.internal
      uid: 9af78ea6-d6eb-42e9-9c06-2d05ac659166
    resourceVersion: "159317"
    uid: 33e60207-1aa8-459f-a8af-b346cd0971fe
  spec:
    sourcePod: network-check-source-6f78d59f99-z6b8h
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T17:20:52Z"
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.93455ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:30:52Z"
    - latency: 1.890712ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:29:52Z"
    - latency: 1.893293ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:28:52Z"
    - latency: 2.077134ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:27:52Z"
    - latency: 1.885965ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:26:52Z"
    - latency: 1.878579ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:25:52Z"
    - latency: 2.078172ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:24:52Z"
    - latency: 1.777651ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:23:52Z"
    - latency: 2.060064ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:22:52Z"
    - latency: 2.79245ms
      message: 'network-check-target-ip-10-0-143-147: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:21:52Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T17:13:51Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-222-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-222.ec2.internal
      uid: 9af78ea6-d6eb-42e9-9c06-2d05ac659166
    resourceVersion: "159898"
    uid: ebca6630-3ea9-40f2-9666-8a861b6d37a9
  spec:
    sourcePod: network-check-source-6f78d59f99-z6b8h
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T17:19:52Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.07033ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:31:52Z"
    - latency: 2.279607ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:31:52Z"
    - latency: 972.374µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:30:52Z"
    - latency: 1.900525ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:30:52Z"
    - latency: 1.159159ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:29:52Z"
    - latency: 1.689587ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:29:52Z"
    - latency: 1.117204ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:28:52Z"
    - latency: 1.820136ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:28:52Z"
    - latency: 1.335237ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T18:27:52Z"
    - latency: 2.020404ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T18:27:52Z"
kind: List
metadata:
  resourceVersion: ""