apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:14:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-113-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-113.ec2.internal
      uid: 649a0036-db9b-4c5e-bc19-89e543b9a617
    resourceVersion: "69216"
    uid: ef5c2f64-c1e8-4ce9-b755-968ce80b313d
  spec:
    sourcePod: network-check-source-6f8b768455-jdbvb
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:21:45Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.075632ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:49:45Z"
    - latency: 1.179531ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:48:45Z"
    - latency: 1.095292ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:47:45Z"
    - latency: 989.137µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:46:45Z"
    - latency: 1.034363ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:45:45Z"
    - latency: 918.102µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:44:45Z"
    - latency: 1.178389ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:43:45Z"
    - latency: 1.107071ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:42:45Z"
    - latency: 1.184049ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:41:45Z"
    - latency: 1.044716ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:40:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:14:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-113-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-113.ec2.internal
      uid: 649a0036-db9b-4c5e-bc19-89e543b9a617
    resourceVersion: "70213"
    uid: 0fe4ae6f-ab29-4e9e-8aa7-056c06ee6f3c
  spec:
    sourcePod: network-check-source-6f8b768455-jdbvb
    targetEndpoint: a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:20:45Z"
      message: 'load-balancer-api-external: tcp connection to a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.27677ms
      message: 'load-balancer-api-external: tcp connection to a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:50:45Z"
    - latency: 8.647276ms
      message: 'load-balancer-api-external: resolved host name a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:50:45Z"
    - latency: 3.801575ms
      message: 'load-balancer-api-external: tcp connection to a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:49:45Z"
    - latency: 8.934059ms
      message: 'load-balancer-api-external: resolved host name a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:49:45Z"
    - latency: 3.821593ms
      message: 'load-balancer-api-external: tcp connection to a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:48:45Z"
    - latency: 8.587507ms
      message: 'load-balancer-api-external: resolved host name a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:48:45Z"
    - latency: 4.38621ms
      message: 'load-balancer-api-external: tcp connection to a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:47:45Z"
    - latency: 8.258405ms
      message: 'load-balancer-api-external: resolved host name a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:47:45Z"
    - latency: 4.453787ms
      message: 'load-balancer-api-external: tcp connection to a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:46:45Z"
    - latency: 7.854934ms
      message: 'load-balancer-api-external: resolved host name a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:46:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:14:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-113-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-113.ec2.internal
      uid: 649a0036-db9b-4c5e-bc19-89e543b9a617
    resourceVersion: "70214"
    uid: ee043884-d313-44a7-a14d-9a979b08d583
  spec:
    sourcePod: network-check-source-6f8b768455-jdbvb
    targetEndpoint: a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:20:45Z"
      message: 'load-balancer-api-internal: tcp connection to a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.243954ms
      message: 'load-balancer-api-internal: tcp connection to a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:50:45Z"
    - latency: 8.56572ms
      message: 'load-balancer-api-internal: resolved host name a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:50:45Z"
    - latency: 3.875847ms
      message: 'load-balancer-api-internal: tcp connection to a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:49:45Z"
    - latency: 8.984139ms
      message: 'load-balancer-api-internal: resolved host name a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:49:45Z"
    - latency: 5.709925ms
      message: 'load-balancer-api-internal: tcp connection to a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:48:45Z"
    - latency: 8.653081ms
      message: 'load-balancer-api-internal: resolved host name a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:48:45Z"
    - latency: 4.42687ms
      message: 'load-balancer-api-internal: tcp connection to a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:47:45Z"
    - latency: 8.323522ms
      message: 'load-balancer-api-internal: resolved host name a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:47:45Z"
    - latency: 4.43393ms
      message: 'load-balancer-api-internal: tcp connection to a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:46:45Z"
    - latency: 7.75508ms
      message: 'load-balancer-api-internal: resolved host name a3767fb03bdbb43e887f0d01e283303c-bedef0599ff2bfcb.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:46:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:14:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-113-to-network-check-target-ip-10-0-137-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-113.ec2.internal
      uid: 649a0036-db9b-4c5e-bc19-89e543b9a617
    resourceVersion: "69214"
    uid: 8993429b-6eb6-4e4a-91af-396700d04099
  spec:
    sourcePod: network-check-source-6f8b768455-jdbvb
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:21:45Z"
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.399772ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:49:45Z"
    - latency: 2.442117ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:48:45Z"
    - latency: 2.370237ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:47:45Z"
    - latency: 2.273489ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:46:45Z"
    - latency: 2.564826ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:45:45Z"
    - latency: 2.115338ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:44:45Z"
    - latency: 2.074774ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:43:45Z"
    - latency: 2.619219ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:42:45Z"
    - latency: 2.399866ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:41:45Z"
    - latency: 2.524514ms
      message: 'network-check-target-ip-10-0-137-138: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:40:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:14:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-113-to-network-check-target-ip-10-0-140-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-113.ec2.internal
      uid: 649a0036-db9b-4c5e-bc19-89e543b9a617
    resourceVersion: "69213"
    uid: 4cf8e325-d4ce-422b-a9a0-449fd93081a7
  spec:
    sourcePod: network-check-source-6f8b768455-jdbvb
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:21:45Z"
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 935.782µs
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:49:45Z"
    - latency: 978.708µs
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:48:45Z"
    - latency: 1.013462ms
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:47:45Z"
    - latency: 955.042µs
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:46:45Z"
    - latency: 1.206226ms
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:45:45Z"
    - latency: 1.078105ms
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:44:45Z"
    - latency: 904.22µs
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:43:45Z"
    - latency: 1.040086ms
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:42:45Z"
    - latency: 1.129246ms
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:41:45Z"
    - latency: 921.482µs
      message: 'network-check-target-ip-10-0-140-113: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:40:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:14:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-113-to-network-check-target-ip-10-0-141-188
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-113.ec2.internal
      uid: 649a0036-db9b-4c5e-bc19-89e543b9a617
    resourceVersion: "69215"
    uid: af15c0f6-6245-4ea8-b476-2c69b76ac115
  spec:
    sourcePod: network-check-source-6f8b768455-jdbvb
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:21:45Z"
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.435947ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:49:45Z"
    - latency: 2.328961ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:48:45Z"
    - latency: 2.296123ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:47:45Z"
    - latency: 2.470461ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:46:45Z"
    - latency: 2.139957ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:45:45Z"
    - latency: 2.534938ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:44:45Z"
    - latency: 2.16265ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:43:45Z"
    - latency: 2.771167ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:42:45Z"
    - latency: 2.468858ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:41:45Z"
    - latency: 2.345139ms
      message: 'network-check-target-ip-10-0-141-188: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:40:45Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-15T21:14:43Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-113-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-113.ec2.internal
      uid: 649a0036-db9b-4c5e-bc19-89e543b9a617
    resourceVersion: "70212"
    uid: bd6bb985-2ebd-4980-993f-aabd27a34097
  spec:
    sourcePod: network-check-source-6f8b768455-jdbvb
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-15T21:20:45Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 982.067µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:50:45Z"
    - latency: 1.755282ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:50:45Z"
    - latency: 1.31229ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:49:45Z"
    - latency: 1.929282ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:49:45Z"
    - latency: 1.077088ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:48:45Z"
    - latency: 2.224029ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:48:45Z"
    - latency: 952.637µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:47:45Z"
    - latency: 1.63025ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:47:45Z"
    - latency: 888.764µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-15T21:46:45Z"
    - latency: 1.753723ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-15T21:46:45Z"
kind: List
metadata:
  resourceVersion: ""