apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T20:17:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-120-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-120.us-west-2.compute.internal
      uid: 1c2ef97d-ed8d-4989-a1b5-e98efc6a22c6
    resourceVersion: "75115"
    uid: e4c9ecfa-ff01-4970-9d63-ad485cfb3956
  spec:
    sourcePod: network-check-source-6f78d59f99-6tfzr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T20:24:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.298135ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:59:23Z"
    - latency: 1.299526ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:58:23Z"
    - latency: 1.061834ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:57:23Z"
    - latency: 1.600307ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:56:23Z"
    - latency: 1.126315ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:55:23Z"
    - latency: 886.72µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:54:23Z"
    - latency: 1.243598ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:53:23Z"
    - latency: 1.210374ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:52:23Z"
    - latency: 980.751µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:51:23Z"
    - latency: 1.206274ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:50:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T20:17:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-120-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-120.us-west-2.compute.internal
      uid: 1c2ef97d-ed8d-4989-a1b5-e98efc6a22c6
    resourceVersion: "75116"
    uid: a14d75fd-04c8-4020-9990-0b908fc92067
  spec:
    sourcePod: network-check-source-6f78d59f99-6tfzr
    targetEndpoint: a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T20:23:23Z"
      message: 'load-balancer-api-external: tcp connection to a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.695127ms
      message: 'load-balancer-api-external: tcp connection to a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:59:23Z"
    - latency: 7.54711ms
      message: 'load-balancer-api-external: resolved host name a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:59:23Z"
    - latency: 56.125332ms
      message: 'load-balancer-api-external: tcp connection to a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:58:23Z"
    - latency: 7.137929ms
      message: 'load-balancer-api-external: resolved host name a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:58:23Z"
    - latency: 55.010049ms
      message: 'load-balancer-api-external: tcp connection to a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:57:23Z"
    - latency: 7.15437ms
      message: 'load-balancer-api-external: resolved host name a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:57:23Z"
    - latency: 57.026788ms
      message: 'load-balancer-api-external: tcp connection to a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:56:23Z"
    - latency: 7.083539ms
      message: 'load-balancer-api-external: resolved host name a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:56:23Z"
    - latency: 56.108165ms
      message: 'load-balancer-api-external: tcp connection to a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:55:23Z"
    - latency: 10.069431ms
      message: 'load-balancer-api-external: resolved host name a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:55:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T20:17:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-120-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-120.us-west-2.compute.internal
      uid: 1c2ef97d-ed8d-4989-a1b5-e98efc6a22c6
    resourceVersion: "75117"
    uid: ec37afd4-6c4f-4339-be12-4b765b99c7f5
  spec:
    sourcePod: network-check-source-6f78d59f99-6tfzr
    targetEndpoint: a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T20:23:27Z"
      message: 'load-balancer-api-internal: tcp connection to a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.769386ms
      message: 'load-balancer-api-internal: tcp connection to a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:59:23Z"
    - latency: 7.437057ms
      message: 'load-balancer-api-internal: resolved host name a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:59:23Z"
    - latency: 51.169519ms
      message: 'load-balancer-api-internal: tcp connection to a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:58:23Z"
    - latency: 7.046907ms
      message: 'load-balancer-api-internal: resolved host name a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:58:23Z"
    - latency: 51.283089ms
      message: 'load-balancer-api-internal: tcp connection to a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:57:23Z"
    - latency: 7.026119ms
      message: 'load-balancer-api-internal: resolved host name a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:57:23Z"
    - latency: 51.55621ms
      message: 'load-balancer-api-internal: tcp connection to a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:56:23Z"
    - latency: 7.006272ms
      message: 'load-balancer-api-internal: resolved host name a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:56:23Z"
    - latency: 56.735844ms
      message: 'load-balancer-api-internal: tcp connection to a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:55:23Z"
    - latency: 9.998016ms
      message: 'load-balancer-api-internal: resolved host name a005d902b89f44e8db632ef0d2b795eb-22154488e9922e7d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:55:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T20:17:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-120-to-network-check-target-ip-10-0-134-201
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-120.us-west-2.compute.internal
      uid: 1c2ef97d-ed8d-4989-a1b5-e98efc6a22c6
    resourceVersion: "75113"
    uid: f6d276ea-52b8-4668-9bc8-87546ccddbe3
  spec:
    sourcePod: network-check-source-6f78d59f99-6tfzr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T20:24:23Z"
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.522296ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:59:23Z"
    - latency: 2.359921ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:58:23Z"
    - latency: 2.548997ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:57:23Z"
    - latency: 2.314633ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:56:23Z"
    - latency: 2.491119ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:55:23Z"
    - latency: 2.210615ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:54:23Z"
    - latency: 2.354731ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:53:23Z"
    - latency: 2.816496ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:52:23Z"
    - latency: 2.396571ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:51:23Z"
    - latency: 2.491081ms
      message: 'network-check-target-ip-10-0-134-201: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:50:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T20:17:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-120-to-network-check-target-ip-10-0-134-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-120.us-west-2.compute.internal
      uid: 1c2ef97d-ed8d-4989-a1b5-e98efc6a22c6
    resourceVersion: "75112"
    uid: f2c43622-0a0a-42b6-9814-72a69b6a7ec0
  spec:
    sourcePod: network-check-source-6f78d59f99-6tfzr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T20:24:23Z"
      message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.872269ms
      message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:59:23Z"
    - latency: 2.000969ms
      message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:58:23Z"
    - latency: 1.964149ms
      message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:57:23Z"
    - latency: 2.02435ms
      message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:56:23Z"
    - latency: 1.979097ms
      message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:55:23Z"
    - latency: 2.052499ms
      message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:54:23Z"
    - latency: 2.026873ms
      message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:53:23Z"
    - latency: 1.997584ms
      message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:52:23Z"
    - latency: 1.950058ms
      message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:51:23Z"
    - latency: 2.206808ms
      message: 'network-check-target-ip-10-0-134-206: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:50:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T20:17:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-120-to-network-check-target-ip-10-0-140-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-120.us-west-2.compute.internal
      uid: 1c2ef97d-ed8d-4989-a1b5-e98efc6a22c6
    resourceVersion: "75111"
    uid: a7ad78be-c48d-452f-8f6e-8803f413d7a9
  spec:
    sourcePod: network-check-source-6f78d59f99-6tfzr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T20:24:23Z"
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.494µs
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:59:23Z"
    - latency: 925.936µs
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:58:23Z"
    - latency: 1.012659ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:57:23Z"
    - latency: 941.269µs
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:56:23Z"
    - latency: 1.095681ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:55:23Z"
    - latency: 1.067925ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:54:23Z"
    - latency: 1.850424ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:53:23Z"
    - latency: 858.089µs
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:52:23Z"
    - latency: 940.406µs
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:51:23Z"
    - latency: 1.053057ms
      message: 'network-check-target-ip-10-0-140-120: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:50:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T20:17:23Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-120-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-120.us-west-2.compute.internal
      uid: 1c2ef97d-ed8d-4989-a1b5-e98efc6a22c6
    resourceVersion: "75114"
    uid: 45f2dd86-2379-4407-909e-9907180065c8
  spec:
    sourcePod: network-check-source-6f78d59f99-6tfzr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T20:23:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 888.688µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:59:23Z"
    - latency: 1.930357ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:59:23Z"
    - latency: 1.044065ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:58:23Z"
    - latency: 1.96232ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:58:23Z"
    - latency: 965.574µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:57:23Z"
    - latency: 1.745206ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:57:23Z"
    - latency: 1.141919ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:56:23Z"
    - latency: 2.292979ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:56:23Z"
    - latency: 1.064396ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T20:55:23Z"
    - latency: 1.980074ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T20:55:23Z"
kind: List
metadata:
  resourceVersion: ""