apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T11:10:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-54-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-54.ec2.internal
      uid: 7f21ac8b-9ca8-429e-93a8-6a0b534faf91
    resourceVersion: "19165"
    uid: daaf4554-206f-4fcc-b271-540fe1ac6b2c
  spec:
    sourcePod: network-check-source-dbd9cf844-9zlrm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T11:17:04Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.098851ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:31:04Z"
    - latency: 1.348858ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:30:04Z"
    - latency: 968.661µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:29:04Z"
    - latency: 1.174008ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:28:04Z"
    - latency: 979.634µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:27:04Z"
    - latency: 1.173678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:26:04Z"
    - latency: 968.408µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:25:04Z"
    - latency: 1.059035ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:24:04Z"
    - latency: 876.052µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:23:04Z"
    - latency: 935.111µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:22:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T11:10:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-54-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-54.ec2.internal
      uid: 7f21ac8b-9ca8-429e-93a8-6a0b534faf91
    resourceVersion: "20360"
    uid: a926afad-7edb-44af-ad62-bb13625748f3
  spec:
    sourcePod: network-check-source-dbd9cf844-9zlrm
    targetEndpoint: a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T11:16:04Z"
      message: 'load-balancer-api-external: tcp connection to a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.930088ms
      message: 'load-balancer-api-external: tcp connection to a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:34:04Z"
    - latency: 7.971857ms
      message: 'load-balancer-api-external: resolved host name a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:34:04Z"
    - latency: 4.602522ms
      message: 'load-balancer-api-external: tcp connection to a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:33:04Z"
    - latency: 9.059383ms
      message: 'load-balancer-api-external: resolved host name a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:33:04Z"
    - latency: 5.032928ms
      message: 'load-balancer-api-external: tcp connection to a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:32:04Z"
    - latency: 13.355031ms
      message: 'load-balancer-api-external: resolved host name a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:32:04Z"
    - latency: 5.197347ms
      message: 'load-balancer-api-external: tcp connection to a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:31:04Z"
    - latency: 11.739587ms
      message: 'load-balancer-api-external: resolved host name a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:31:04Z"
    - latency: 4.659772ms
      message: 'load-balancer-api-external: tcp connection to a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:30:04Z"
    - latency: 8.398107ms
      message: 'load-balancer-api-external: resolved host name a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:30:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T11:10:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-54-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-54.ec2.internal
      uid: 7f21ac8b-9ca8-429e-93a8-6a0b534faf91
    resourceVersion: "20359"
    uid: bf5c3f25-7ec0-4af8-bc8b-e878b6775194
  spec:
    sourcePod: network-check-source-dbd9cf844-9zlrm
    targetEndpoint: a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T11:16:04Z"
      message: 'load-balancer-api-internal: tcp connection to a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.887825ms
      message: 'load-balancer-api-internal: tcp connection to a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:34:04Z"
    - latency: 8.065416ms
      message: 'load-balancer-api-internal: resolved host name a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:34:04Z"
    - latency: 4.472484ms
      message: 'load-balancer-api-internal: tcp connection to a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:33:04Z"
    - latency: 9.134077ms
      message: 'load-balancer-api-internal: resolved host name a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:33:04Z"
    - latency: 5.007211ms
      message: 'load-balancer-api-internal: tcp connection to a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:32:04Z"
    - latency: 13.458673ms
      message: 'load-balancer-api-internal: resolved host name a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:32:04Z"
    - latency: 5.205071ms
      message: 'load-balancer-api-internal: tcp connection to a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:31:04Z"
    - latency: 11.842895ms
      message: 'load-balancer-api-internal: resolved host name a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:31:04Z"
    - latency: 4.628995ms
      message: 'load-balancer-api-internal: tcp connection to a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:30:04Z"
    - latency: 8.472306ms
      message: 'load-balancer-api-internal: resolved host name a33674d2927fa42818a5f62e4578a84d-1335f8a6ae3cc243.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:30:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T11:10:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-54-to-network-check-target-ip-10-0-130-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-54.ec2.internal
      uid: 7f21ac8b-9ca8-429e-93a8-6a0b534faf91
    resourceVersion: "19163"
    uid: 844b6c2d-bffa-4e39-b0e8-84c4906a1968
  spec:
    sourcePod: network-check-source-dbd9cf844-9zlrm
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T11:17:04Z"
      message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.83261ms
      message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:31:04Z"
    - latency: 1.719758ms
      message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:30:04Z"
    - latency: 1.707724ms
      message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:29:04Z"
    - latency: 1.596882ms
      message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:28:04Z"
    - latency: 1.795751ms
      message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:27:04Z"
    - latency: 1.438483ms
      message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:26:04Z"
    - latency: 1.599031ms
      message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:25:04Z"
    - latency: 1.723631ms
      message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:24:04Z"
    - latency: 1.525073ms
      message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:23:04Z"
    - latency: 1.692906ms
      message: 'network-check-target-ip-10-0-130-8: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:22:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T11:10:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-54-to-network-check-target-ip-10-0-131-194
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-54.ec2.internal
      uid: 7f21ac8b-9ca8-429e-93a8-6a0b534faf91
    resourceVersion: "19164"
    uid: 9b72a1b9-5c3b-4c9d-9b65-971d79f1b446
  spec:
    sourcePod: network-check-source-dbd9cf844-9zlrm
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T11:17:04Z"
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.074768ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:31:04Z"
    - latency: 1.966594ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:30:04Z"
    - latency: 2.161717ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:29:04Z"
    - latency: 2.163973ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:28:04Z"
    - latency: 2.212961ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:27:04Z"
    - latency: 2.036196ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:26:04Z"
    - latency: 2.005073ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:25:04Z"
    - latency: 1.977229ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:24:04Z"
    - latency: 2.262285ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:23:04Z"
    - latency: 2.203704ms
      message: 'network-check-target-ip-10-0-131-194: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:22:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T11:10:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-54-to-network-check-target-ip-10-0-134-54
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-54.ec2.internal
      uid: 7f21ac8b-9ca8-429e-93a8-6a0b534faf91
    resourceVersion: "19162"
    uid: b2a9d232-12a9-4ff9-9ba2-1f3f127bc837
  spec:
    sourcePod: network-check-source-dbd9cf844-9zlrm
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T11:17:04Z"
      message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 861.306µs
      message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:31:04Z"
    - latency: 1.535647ms
      message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:30:04Z"
    - latency: 980.414µs
      message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:29:04Z"
    - latency: 851.726µs
      message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:28:04Z"
    - latency: 1.171778ms
      message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:27:04Z"
    - latency: 836.322µs
      message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:26:04Z"
    - latency: 1.356774ms
      message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:25:04Z"
    - latency: 752.193µs
      message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:24:04Z"
    - latency: 859.638µs
      message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:23:04Z"
    - latency: 1.150086ms
      message: 'network-check-target-ip-10-0-134-54: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:22:04Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-09T11:10:02Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-54-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-54.ec2.internal
      uid: 7f21ac8b-9ca8-429e-93a8-6a0b534faf91
    resourceVersion: "20358"
    uid: 3a8df243-0faa-466b-a147-562688a9067c
  spec:
    sourcePod: network-check-source-dbd9cf844-9zlrm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-09T11:16:04Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.080225ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:34:04Z"
    - latency: 1.730692ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:34:04Z"
    - latency: 773.38µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:33:04Z"
    - latency: 2.501577ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:33:04Z"
    - latency: 783.229µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:32:04Z"
    - latency: 1.619992ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:32:04Z"
    - latency: 871.672µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:31:04Z"
    - latency: 1.90026ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:31:04Z"
    - latency: 760.116µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-09T11:30:04Z"
    - latency: 1.88478ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-09T11:30:04Z"
kind: List
metadata:
  resourceVersion: ""