apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:28:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 1b0bf0a0-3e86-4c82-976c-7699d15ecdf7
    resourceVersion: "33363"
    uid: 79aadaca-3f20-49a5-867f-5f47987f0d5a
  spec:
    sourcePod: network-check-source-989f8b8dc-mr7p5
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:35:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.055697ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:49:48Z"
    - latency: 861.503µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:48Z"
    - latency: 766.688µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:48Z"
    - latency: 1.21872ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:48Z"
    - latency: 1.282041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:48Z"
    - latency: 1.168343ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 699.148µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 880.853µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 1.061047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:48Z"
    - latency: 1.317704ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:28:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 1b0bf0a0-3e86-4c82-976c-7699d15ecdf7
    resourceVersion: "31306"
    uid: a99e2c2e-678e-4b03-a581-62f5f9adf970
  spec:
    sourcePod: network-check-source-989f8b8dc-mr7p5
    targetEndpoint: a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:34:48Z"
      message: 'load-balancer-api-external: tcp connection to a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.125077ms
      message: 'load-balancer-api-external: tcp connection to a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:48Z"
    - latency: 8.879554ms
      message: 'load-balancer-api-external: resolved host name a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:46:48Z"
    - latency: 3.403319ms
      message: 'load-balancer-api-external: tcp connection to a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:48Z"
    - latency: 8.151477ms
      message: 'load-balancer-api-external: resolved host name a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:45:48Z"
    - latency: 4.111914ms
      message: 'load-balancer-api-external: tcp connection to a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 9.402688ms
      message: 'load-balancer-api-external: resolved host name a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 4.946418ms
      message: 'load-balancer-api-external: tcp connection to a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 8.221573ms
      message: 'load-balancer-api-external: resolved host name a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 3.099177ms
      message: 'load-balancer-api-external: tcp connection to a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 7.060507ms
      message: 'load-balancer-api-external: resolved host name a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:42:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:28:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 1b0bf0a0-3e86-4c82-976c-7699d15ecdf7
    resourceVersion: "31305"
    uid: 3cd78744-a957-4542-808c-9f9968b063a2
  spec:
    sourcePod: network-check-source-989f8b8dc-mr7p5
    targetEndpoint: a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:34:48Z"
      message: 'load-balancer-api-internal: tcp connection to a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.959797ms
      message: 'load-balancer-api-internal: tcp connection to a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:48Z"
    - latency: 8.843064ms
      message: 'load-balancer-api-internal: resolved host name a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:46:48Z"
    - latency: 3.36269ms
      message: 'load-balancer-api-internal: tcp connection to a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:48Z"
    - latency: 8.189923ms
      message: 'load-balancer-api-internal: resolved host name a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:45:48Z"
    - latency: 3.989858ms
      message: 'load-balancer-api-internal: tcp connection to a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 9.470468ms
      message: 'load-balancer-api-internal: resolved host name a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 4.161221ms
      message: 'load-balancer-api-internal: tcp connection to a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 8.256998ms
      message: 'load-balancer-api-internal: resolved host name a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 5.123988ms
      message: 'load-balancer-api-internal: tcp connection to a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 7.133086ms
      message: 'load-balancer-api-internal: resolved host name a5800ac8383db40efb0390a2b1bae36a-9861bd89d80fb37c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:42:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:28:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-network-check-target-ip-10-0-133-135
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 1b0bf0a0-3e86-4c82-976c-7699d15ecdf7
    resourceVersion: "33340"
    uid: 5980fbba-e4af-49ad-9ca8-bf03f9c0d5c7
  spec:
    sourcePod: network-check-source-989f8b8dc-mr7p5
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:35:48Z"
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.087871ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:49:48Z"
    - latency: 2.28371ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:48Z"
    - latency: 1.864808ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:48Z"
    - latency: 2.349975ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:48Z"
    - latency: 2.090455ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:48Z"
    - latency: 1.882622ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 1.821413ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 2.396811ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 2.197499ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:48Z"
    - latency: 1.915801ms
      message: 'network-check-target-ip-10-0-133-135: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:28:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-network-check-target-ip-10-0-138-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 1b0bf0a0-3e86-4c82-976c-7699d15ecdf7
    resourceVersion: "33341"
    uid: 4893ce90-df69-4c34-a782-c093548e5790
  spec:
    sourcePod: network-check-source-989f8b8dc-mr7p5
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:35:48Z"
      message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.069933ms
      message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:49:48Z"
    - latency: 1.953973ms
      message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:48Z"
    - latency: 1.853877ms
      message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:48Z"
    - latency: 1.880783ms
      message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:48Z"
    - latency: 1.897516ms
      message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:48Z"
    - latency: 1.75271ms
      message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 1.9269ms
      message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 1.80458ms
      message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 1.908139ms
      message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:48Z"
    - latency: 1.827581ms
      message: 'network-check-target-ip-10-0-138-110: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:28:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-network-check-target-ip-10-0-139-3
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 1b0bf0a0-3e86-4c82-976c-7699d15ecdf7
    resourceVersion: "33355"
    uid: 8792d21d-61bc-4614-be08-73746a796ddd
  spec:
    sourcePod: network-check-source-989f8b8dc-mr7p5
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:35:48Z"
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 944.958µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:49:48Z"
    - latency: 1.089783ms
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:48:48Z"
    - latency: 980.723µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:47:48Z"
    - latency: 864.825µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:48Z"
    - latency: 821.073µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:48Z"
    - latency: 842.997µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 966.785µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 853.507µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 1.224602ms
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:48Z"
    - latency: 978.9µs
      message: 'network-check-target-ip-10-0-139-3: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:28:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-3-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-3.ec2.internal
      uid: 1b0bf0a0-3e86-4c82-976c-7699d15ecdf7
    resourceVersion: "31304"
    uid: 0e68a348-a35e-4f8d-92d9-0222814a22f4
  spec:
    sourcePod: network-check-source-989f8b8dc-mr7p5
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:34:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.010021ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:46:48Z"
    - latency: 1.824769ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:46:48Z"
    - latency: 784.065µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:45:48Z"
    - latency: 1.702285ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:45:48Z"
    - latency: 900.279µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 1.865114ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 844.412µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 1.884391ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 907.32µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 1.679261ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:42:48Z"
kind: List
metadata:
  resourceVersion: ""