apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:57:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: e56d89a7-d9fa-497a-9862-55ee3d754491
    resourceVersion: "54162"
    uid: 919d33c7-9cc7-4d6b-854e-1291921cfb0c
  spec:
    sourcePod: network-check-source-685456655f-rmcsw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:04:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.049353ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:20Z"
    - latency: 1.101505ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:20Z"
    - latency: 1.306216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:20Z"
    - latency: 869.081µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:20Z"
    - latency: 1.203001ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:20Z"
    - latency: 1.545665ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:20:20Z"
    - latency: 1.028942ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:19:20Z"
    - latency: 1.090477ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:18:20Z"
    - latency: 1.123353ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:17:20Z"
    - latency: 1.262652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:16:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:57:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: e56d89a7-d9fa-497a-9862-55ee3d754491
    resourceVersion: "55845"
    uid: aa41ab24-1fe1-442e-ade5-3a8f78bc83f1
  spec:
    sourcePod: network-check-source-685456655f-rmcsw
    targetEndpoint: a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:03:20Z"
      message: 'load-balancer-api-external: tcp connection to a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.566959ms
      message: 'load-balancer-api-external: tcp connection to a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:27:20Z"
    - latency: 8.300884ms
      message: 'load-balancer-api-external: resolved host name a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:27:20Z"
    - latency: 4.742423ms
      message: 'load-balancer-api-external: tcp connection to a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:20Z"
    - latency: 9.869296ms
      message: 'load-balancer-api-external: resolved host name a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:26:20Z"
    - latency: 4.621016ms
      message: 'load-balancer-api-external: tcp connection to a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:20Z"
    - latency: 7.441099ms
      message: 'load-balancer-api-external: resolved host name a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:25:20Z"
    - latency: 4.902391ms
      message: 'load-balancer-api-external: tcp connection to a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:20Z"
    - latency: 7.420587ms
      message: 'load-balancer-api-external: resolved host name a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:24:20Z"
    - latency: 5.033008ms
      message: 'load-balancer-api-external: tcp connection to a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:20Z"
    - latency: 6.705059ms
      message: 'load-balancer-api-external: resolved host name a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:23:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:57:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: e56d89a7-d9fa-497a-9862-55ee3d754491
    resourceVersion: "55846"
    uid: d00254f1-8170-4827-bdb8-eea65183d67b
  spec:
    sourcePod: network-check-source-685456655f-rmcsw
    targetEndpoint: a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:03:20Z"
      message: 'load-balancer-api-internal: tcp connection to a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.679912ms
      message: 'load-balancer-api-internal: tcp connection to a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:27:20Z"
    - latency: 8.273091ms
      message: 'load-balancer-api-internal: resolved host name a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:27:20Z"
    - latency: 4.746064ms
      message: 'load-balancer-api-internal: tcp connection to a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:20Z"
    - latency: 9.810164ms
      message: 'load-balancer-api-internal: resolved host name a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:26:20Z"
    - latency: 4.668113ms
      message: 'load-balancer-api-internal: tcp connection to a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:20Z"
    - latency: 7.473792ms
      message: 'load-balancer-api-internal: resolved host name a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:25:20Z"
    - latency: 4.889984ms
      message: 'load-balancer-api-internal: tcp connection to a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:20Z"
    - latency: 7.448041ms
      message: 'load-balancer-api-internal: resolved host name a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:24:20Z"
    - latency: 4.996303ms
      message: 'load-balancer-api-internal: tcp connection to a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:20Z"
    - latency: 6.771838ms
      message: 'load-balancer-api-internal: resolved host name a6b6849e55ba04f8c89a50b8c30edad2-6d61746e9f744ae9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:23:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:57:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-network-check-target-ip-10-0-141-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: e56d89a7-d9fa-497a-9862-55ee3d754491
    resourceVersion: "54160"
    uid: 5ce35a26-1543-4149-8726-49d234558d47
  spec:
    sourcePod: network-check-source-685456655f-rmcsw
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:04:20Z"
      message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.474093ms
      message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:20Z"
    - latency: 2.61317ms
      message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:20Z"
    - latency: 2.774865ms
      message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:20Z"
    - latency: 2.395808ms
      message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:20Z"
    - latency: 2.717888ms
      message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:20Z"
    - latency: 2.629153ms
      message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:20:20Z"
    - latency: 2.164855ms
      message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:19:20Z"
    - latency: 2.480902ms
      message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:18:20Z"
    - latency: 2.840504ms
      message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:17:20Z"
    - latency: 2.440096ms
      message: 'network-check-target-ip-10-0-141-58: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:16:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:57:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-network-check-target-ip-10-0-142-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: e56d89a7-d9fa-497a-9862-55ee3d754491
    resourceVersion: "54159"
    uid: 89d2aab2-7a4d-4433-881c-edb0943c7c0b
  spec:
    sourcePod: network-check-source-685456655f-rmcsw
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:04:20Z"
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.947µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:20Z"
    - latency: 1.009037ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:20Z"
    - latency: 1.07462ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:20Z"
    - latency: 1.104697ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:20Z"
    - latency: 1.041124ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:20Z"
    - latency: 1.440488ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:20:20Z"
    - latency: 987.918µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:19:20Z"
    - latency: 1.070664ms
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:18:20Z"
    - latency: 938.372µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:17:20Z"
    - latency: 865.466µs
      message: 'network-check-target-ip-10-0-142-1: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:16:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:57:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-network-check-target-ip-10-0-143-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: e56d89a7-d9fa-497a-9862-55ee3d754491
    resourceVersion: "54161"
    uid: 4cabee88-42c6-484b-8832-43beff81010d
  spec:
    sourcePod: network-check-source-685456655f-rmcsw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:04:20Z"
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.714019ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:20Z"
    - latency: 2.506322ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:20Z"
    - latency: 2.486277ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:20Z"
    - latency: 2.347281ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:22:20Z"
    - latency: 2.508658ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:21:20Z"
    - latency: 3.007181ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:20:20Z"
    - latency: 2.031082ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:19:20Z"
    - latency: 2.54159ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:18:20Z"
    - latency: 2.360226ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:17:20Z"
    - latency: 2.306805ms
      message: 'network-check-target-ip-10-0-143-132: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:16:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-07T12:57:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-1-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-1.ec2.internal
      uid: e56d89a7-d9fa-497a-9862-55ee3d754491
    resourceVersion: "55844"
    uid: 1cb28e63-ff9a-4da1-9162-103c5c71c64a
  spec:
    sourcePod: network-check-source-685456655f-rmcsw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-07T13:03:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.276668ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:27:20Z"
    - latency: 2.222369ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:27:20Z"
    - latency: 868.532µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:26:20Z"
    - latency: 1.960224ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:26:20Z"
    - latency: 957.857µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:25:20Z"
    - latency: 2.002367ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:25:20Z"
    - latency: 1.003684ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:24:20Z"
    - latency: 1.897041ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:24:20Z"
    - latency: 961.654µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-07T13:23:20Z"
    - latency: 1.702477ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-07T13:23:20Z"
kind: List
metadata:
  resourceVersion: ""