apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:38:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-200-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-200.ec2.internal
      uid: be100c0e-7908-44bb-bb0c-4a8351f08f10
    resourceVersion: "54591"
    uid: 06aae349-a56a-4737-b265-2431c1695772
  spec:
    sourcePod: network-check-source-989f8b8dc-z5d9w
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:45:01Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.108254ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:13:01Z"
    - latency: 1.002333ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:12:01Z"
    - latency: 1.092835ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:01Z"
    - latency: 977.566µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:01Z"
    - latency: 1.30453ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:01Z"
    - latency: 1.124241ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:01Z"
    - latency: 1.409258ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:01Z"
    - latency: 1.837082ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:01Z"
    - latency: 1.386899ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:01Z"
    - latency: 886.015µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:38:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-200-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-200.ec2.internal
      uid: be100c0e-7908-44bb-bb0c-4a8351f08f10
    resourceVersion: "55459"
    uid: e9aeeca5-e941-4ec9-917e-172e0cec9c5a
  spec:
    sourcePod: network-check-source-989f8b8dc-z5d9w
    targetEndpoint: ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:44:01Z"
      message: 'load-balancer-api-external: tcp connection to ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.340198ms
      message: 'load-balancer-api-external: tcp connection to ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:14:01Z"
    - latency: 7.989776ms
      message: 'load-balancer-api-external: resolved host name ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:14:01Z"
    - latency: 6.162236ms
      message: 'load-balancer-api-external: tcp connection to ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:13:01Z"
    - latency: 8.435103ms
      message: 'load-balancer-api-external: resolved host name ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:13:01Z"
    - latency: 5.213114ms
      message: 'load-balancer-api-external: tcp connection to ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:12:01Z"
    - latency: 8.941372ms
      message: 'load-balancer-api-external: resolved host name ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:12:01Z"
    - latency: 4.842614ms
      message: 'load-balancer-api-external: tcp connection to ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:01Z"
    - latency: 8.988035ms
      message: 'load-balancer-api-external: resolved host name ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:11:01Z"
    - latency: 4.772577ms
      message: 'load-balancer-api-external: tcp connection to ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:01Z"
    - latency: 8.691513ms
      message: 'load-balancer-api-external: resolved host name ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:10:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:38:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-200-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-200.ec2.internal
      uid: be100c0e-7908-44bb-bb0c-4a8351f08f10
    resourceVersion: "55458"
    uid: fc506ee0-bf05-4f5b-8535-c05fab293c4c
  spec:
    sourcePod: network-check-source-989f8b8dc-z5d9w
    targetEndpoint: ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:44:01Z"
      message: 'load-balancer-api-internal: tcp connection to ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.819961ms
      message: 'load-balancer-api-internal: tcp connection to ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:14:01Z"
    - latency: 7.95037ms
      message: 'load-balancer-api-internal: resolved host name ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:14:01Z"
    - latency: 4.944036ms
      message: 'load-balancer-api-internal: tcp connection to ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:13:01Z"
    - latency: 8.405637ms
      message: 'load-balancer-api-internal: resolved host name ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:13:01Z"
    - latency: 3.529845ms
      message: 'load-balancer-api-internal: tcp connection to ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:12:01Z"
    - latency: 9.010588ms
      message: 'load-balancer-api-internal: resolved host name ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:12:01Z"
    - latency: 5.816206ms
      message: 'load-balancer-api-internal: tcp connection to ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:01Z"
    - latency: 9.085546ms
      message: 'load-balancer-api-internal: resolved host name ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:11:01Z"
    - latency: 4.695896ms
      message: 'load-balancer-api-internal: tcp connection to ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:01Z"
    - latency: 8.783772ms
      message: 'load-balancer-api-internal: resolved host name ab139b657877349a193f8796059efe4d-1130fc319a0c744d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:10:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:38:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-200-to-network-check-target-ip-10-0-128-14
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-200.ec2.internal
      uid: be100c0e-7908-44bb-bb0c-4a8351f08f10
    resourceVersion: "54590"
    uid: 26eebd77-8b55-4d72-b3c8-820b9b329cec
  spec:
    sourcePod: network-check-source-989f8b8dc-z5d9w
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:45:01Z"
      message: 'network-check-target-ip-10-0-128-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.767015ms
      message: 'network-check-target-ip-10-0-128-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:13:01Z"
    - latency: 1.878707ms
      message: 'network-check-target-ip-10-0-128-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:12:01Z"
    - latency: 2.177033ms
      message: 'network-check-target-ip-10-0-128-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:01Z"
    - latency: 2.036208ms
      message: 'network-check-target-ip-10-0-128-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:01Z"
    - latency: 2.679603ms
      message: 'network-check-target-ip-10-0-128-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:01Z"
    - latency: 2.04688ms
      message: 'network-check-target-ip-10-0-128-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:01Z"
    - latency: 1.975752ms
      message: 'network-check-target-ip-10-0-128-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:01Z"
    - latency: 2.171323ms
      message: 'network-check-target-ip-10-0-128-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:01Z"
    - latency: 2.253374ms
      message: 'network-check-target-ip-10-0-128-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:01Z"
    - latency: 2.24883ms
      message: 'network-check-target-ip-10-0-128-14: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:38:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-200-to-network-check-target-ip-10-0-128-200
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-200.ec2.internal
      uid: be100c0e-7908-44bb-bb0c-4a8351f08f10
    resourceVersion: "54588"
    uid: 588aaf46-fba6-4f11-8ea4-d4aca8945a39
  spec:
    sourcePod: network-check-source-989f8b8dc-z5d9w
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:45:01Z"
      message: 'network-check-target-ip-10-0-128-200: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 728.922µs
      message: 'network-check-target-ip-10-0-128-200: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:13:01Z"
    - latency: 987.716µs
      message: 'network-check-target-ip-10-0-128-200: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:12:01Z"
    - latency: 1.036936ms
      message: 'network-check-target-ip-10-0-128-200: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:01Z"
    - latency: 1.357628ms
      message: 'network-check-target-ip-10-0-128-200: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:01Z"
    - latency: 1.568693ms
      message: 'network-check-target-ip-10-0-128-200: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:01Z"
    - latency: 820.135µs
      message: 'network-check-target-ip-10-0-128-200: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:01Z"
    - latency: 723.337µs
      message: 'network-check-target-ip-10-0-128-200: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:01Z"
    - latency: 848.204µs
      message: 'network-check-target-ip-10-0-128-200: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:01Z"
    - latency: 812.476µs
      message: 'network-check-target-ip-10-0-128-200: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:01Z"
    - latency: 760.04µs
      message: 'network-check-target-ip-10-0-128-200: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:38:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-200-to-network-check-target-ip-10-0-135-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-200.ec2.internal
      uid: be100c0e-7908-44bb-bb0c-4a8351f08f10
    resourceVersion: "54589"
    uid: 946d7342-3bdf-4313-915f-4a4f7ea0eac0
  spec:
    sourcePod: network-check-source-989f8b8dc-z5d9w
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:45:01Z"
      message: 'network-check-target-ip-10-0-135-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.200786ms
      message: 'network-check-target-ip-10-0-135-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:13:01Z"
    - latency: 2.133208ms
      message: 'network-check-target-ip-10-0-135-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:12:01Z"
    - latency: 2.391667ms
      message: 'network-check-target-ip-10-0-135-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:01Z"
    - latency: 2.314221ms
      message: 'network-check-target-ip-10-0-135-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:01Z"
    - latency: 2.366438ms
      message: 'network-check-target-ip-10-0-135-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:09:01Z"
    - latency: 2.342084ms
      message: 'network-check-target-ip-10-0-135-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:08:01Z"
    - latency: 1.907516ms
      message: 'network-check-target-ip-10-0-135-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:07:01Z"
    - latency: 2.274093ms
      message: 'network-check-target-ip-10-0-135-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:06:01Z"
    - latency: 2.206725ms
      message: 'network-check-target-ip-10-0-135-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:05:01Z"
    - latency: 2.047872ms
      message: 'network-check-target-ip-10-0-135-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:04:01Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:38:00Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-200-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-200.ec2.internal
      uid: be100c0e-7908-44bb-bb0c-4a8351f08f10
    resourceVersion: "55457"
    uid: dced31d7-020c-445c-98d6-59f4813f473e
  spec:
    sourcePod: network-check-source-989f8b8dc-z5d9w
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:44:01Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 869.249µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:14:01Z"
    - latency: 1.706656ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:14:01Z"
    - latency: 1.001271ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:13:01Z"
    - latency: 1.567343ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:13:01Z"
    - latency: 849.853µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:12:01Z"
    - latency: 1.836856ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:12:01Z"
    - latency: 1.079921ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:11:01Z"
    - latency: 2.010346ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:11:01Z"
    - latency: 791.179µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T20:10:01Z"
    - latency: 2.040519ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T20:10:01Z"
kind: List
metadata:
  resourceVersion: ""