apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:31:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-237-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-237.ec2.internal
      uid: 88e62945-6a59-4bc4-b7aa-ff272b4002cd
    resourceVersion: "72272"
    uid: bac7350c-4d43-4b46-ac10-d2afee03134c
  spec:
    sourcePod: network-check-source-7d88cb55d8-f6sz9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:38:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.256377ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:20:42Z"
    - latency: 920.457µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:19:42Z"
    - latency: 1.089849ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:18:42Z"
    - latency: 1.150922ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:17:42Z"
    - latency: 956.769µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:16:42Z"
    - latency: 892.881µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:15:42Z"
    - latency: 1.270158ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:14:42Z"
    - latency: 1.323259ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:13:42Z"
    - latency: 1.29475ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:12:42Z"
    - latency: 950.74µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:11:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:31:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-237-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-237.ec2.internal
      uid: 88e62945-6a59-4bc4-b7aa-ff272b4002cd
    resourceVersion: "71047"
    uid: 97fdc726-e75c-4be3-a7c9-da9c1a62dcac
  spec:
    sourcePod: network-check-source-7d88cb55d8-f6sz9
    targetEndpoint: a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:37:42Z"
      message: 'load-balancer-api-external: tcp connection to a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.949579ms
      message: 'load-balancer-api-external: tcp connection to a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:19:42Z"
    - latency: 8.289395ms
      message: 'load-balancer-api-external: resolved host name a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:19:42Z"
    - latency: 5.104962ms
      message: 'load-balancer-api-external: tcp connection to a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:18:42Z"
    - latency: 11.225555ms
      message: 'load-balancer-api-external: resolved host name a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:18:42Z"
    - latency: 5.60545ms
      message: 'load-balancer-api-external: tcp connection to a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:17:42Z"
    - latency: 9.103648ms
      message: 'load-balancer-api-external: resolved host name a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:17:42Z"
    - latency: 4.796389ms
      message: 'load-balancer-api-external: tcp connection to a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:16:42Z"
    - latency: 19.36269ms
      message: 'load-balancer-api-external: resolved host name a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:16:42Z"
    - latency: 5.906862ms
      message: 'load-balancer-api-external: tcp connection to a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:15:42Z"
    - latency: 10.00466ms
      message: 'load-balancer-api-external: resolved host name a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:15:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:31:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-237-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-237.ec2.internal
      uid: 88e62945-6a59-4bc4-b7aa-ff272b4002cd
    resourceVersion: "71046"
    uid: 1f20c953-3776-448a-9568-a4251d96d88f
  spec:
    sourcePod: network-check-source-7d88cb55d8-f6sz9
    targetEndpoint: a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:37:42Z"
      message: 'load-balancer-api-internal: tcp connection to a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.971071ms
      message: 'load-balancer-api-internal: tcp connection to a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:19:42Z"
    - latency: 8.252762ms
      message: 'load-balancer-api-internal: resolved host name a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:19:42Z"
    - latency: 5.046029ms
      message: 'load-balancer-api-internal: tcp connection to a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:18:42Z"
    - latency: 11.149061ms
      message: 'load-balancer-api-internal: resolved host name a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:18:42Z"
    - latency: 3.833858ms
      message: 'load-balancer-api-internal: tcp connection to a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:17:42Z"
    - latency: 9.029091ms
      message: 'load-balancer-api-internal: resolved host name a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:17:42Z"
    - latency: 4.986513ms
      message: 'load-balancer-api-internal: tcp connection to a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:16:42Z"
    - latency: 21.621195ms
      message: 'load-balancer-api-internal: resolved host name a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:16:42Z"
    - latency: 4.790776ms
      message: 'load-balancer-api-internal: tcp connection to a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:15:42Z"
    - latency: 9.791969ms
      message: 'load-balancer-api-internal: resolved host name a6d1d56ccd0f74549854785fc68ba13b-4831d91d707b7d93.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:15:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:31:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-237-to-network-check-target-ip-10-0-128-237
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-237.ec2.internal
      uid: 88e62945-6a59-4bc4-b7aa-ff272b4002cd
    resourceVersion: "72269"
    uid: 3d0b302e-575b-49ef-9d2f-94ae8fe23a91
  spec:
    sourcePod: network-check-source-7d88cb55d8-f6sz9
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:38:42Z"
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 985.711µs
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:20:42Z"
    - latency: 1.335479ms
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:19:42Z"
    - latency: 946.695µs
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:18:42Z"
    - latency: 945.161µs
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:17:42Z"
    - latency: 4.818289ms
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:16:42Z"
    - latency: 915.006µs
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:15:42Z"
    - latency: 962.221µs
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:14:42Z"
    - latency: 821.503µs
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:13:42Z"
    - latency: 1.536008ms
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:12:42Z"
    - latency: 1.601447ms
      message: 'network-check-target-ip-10-0-128-237: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:11:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:31:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-237-to-network-check-target-ip-10-0-129-235
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-237.ec2.internal
      uid: 88e62945-6a59-4bc4-b7aa-ff272b4002cd
    resourceVersion: "72271"
    uid: f3e5fe96-6b4b-4d35-b3ba-95add502a6a8
  spec:
    sourcePod: network-check-source-7d88cb55d8-f6sz9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:38:42Z"
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.63681ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:20:42Z"
    - latency: 2.062966ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:19:42Z"
    - latency: 2.869303ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:18:42Z"
    - latency: 2.247755ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:17:42Z"
    - latency: 2.561371ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:16:42Z"
    - latency: 2.468484ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:15:42Z"
    - latency: 2.937865ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:14:42Z"
    - latency: 2.086445ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:13:42Z"
    - latency: 2.392746ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:12:42Z"
    - latency: 2.406031ms
      message: 'network-check-target-ip-10-0-129-235: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:11:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:31:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-237-to-network-check-target-ip-10-0-142-24
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-237.ec2.internal
      uid: 88e62945-6a59-4bc4-b7aa-ff272b4002cd
    resourceVersion: "72270"
    uid: 7c806597-f396-4259-9d39-3318be649ee9
  spec:
    sourcePod: network-check-source-7d88cb55d8-f6sz9
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:38:42Z"
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.461644ms
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:20:42Z"
    - latency: 2.239863ms
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:19:42Z"
    - latency: 2.078422ms
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:18:42Z"
    - latency: 2.545685ms
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:17:42Z"
    - latency: 2.291596ms
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:16:42Z"
    - latency: 2.486254ms
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:15:42Z"
    - latency: 2.351564ms
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:14:42Z"
    - latency: 2.348187ms
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:13:42Z"
    - latency: 2.448126ms
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:12:42Z"
    - latency: 2.414736ms
      message: 'network-check-target-ip-10-0-142-24: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:11:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:31:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-237-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-237.ec2.internal
      uid: 88e62945-6a59-4bc4-b7aa-ff272b4002cd
    resourceVersion: "71045"
    uid: d9e804da-cc02-44c1-a757-78fc4c9c284a
  spec:
    sourcePod: network-check-source-7d88cb55d8-f6sz9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:37:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.065958ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:19:42Z"
    - latency: 1.982828ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:19:42Z"
    - latency: 1.02794ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:18:42Z"
    - latency: 2.000891ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:18:42Z"
    - latency: 1.356424ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:17:42Z"
    - latency: 2.033765ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:17:42Z"
    - latency: 4.784569ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:16:42Z"
    - latency: 2.570139ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:16:42Z"
    - latency: 1.157011ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:15:42Z"
    - latency: 2.314495ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:15:42Z"
kind: List
metadata:
  resourceVersion: ""