apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:50:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-53-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-53.ec2.internal
      uid: 0f180e43-3343-4d2c-b5ef-95e59c4cc98f
    resourceVersion: "54630"
    uid: 7447e20a-5580-4207-a11e-8edcf76e222c
  spec:
    sourcePod: network-check-source-989f8b8dc-lxgs9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:57:55Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 996.065µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:25:55Z"
    - latency: 914.864µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:24:55Z"
    - latency: 834.281µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:23:55Z"
    - latency: 955.227µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:22:55Z"
    - latency: 933.785µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:21:55Z"
    - latency: 1.271898ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:20:55Z"
    - latency: 1.040174ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:19:55Z"
    - latency: 1.075104ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:18:55Z"
    - latency: 824.067µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:17:55Z"
    - latency: 1.088737ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:16:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:50:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-53-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-53.ec2.internal
      uid: 0f180e43-3343-4d2c-b5ef-95e59c4cc98f
    resourceVersion: "55619"
    uid: 6f459878-b5ea-46c2-9c9f-485dd677144e
  spec:
    sourcePod: network-check-source-989f8b8dc-lxgs9
    targetEndpoint: a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:56:55Z"
      message: 'load-balancer-api-external: tcp connection to a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.012597ms
      message: 'load-balancer-api-external: tcp connection to a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:26:55Z"
    - latency: 8.898304ms
      message: 'load-balancer-api-external: resolved host name a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:26:55Z"
    - latency: 3.540032ms
      message: 'load-balancer-api-external: tcp connection to a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:25:55Z"
    - latency: 9.912808ms
      message: 'load-balancer-api-external: resolved host name a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:25:55Z"
    - latency: 4.59263ms
      message: 'load-balancer-api-external: tcp connection to a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:24:55Z"
    - latency: 8.887332ms
      message: 'load-balancer-api-external: resolved host name a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:24:55Z"
    - latency: 3.609561ms
      message: 'load-balancer-api-external: tcp connection to a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:23:55Z"
    - latency: 8.504717ms
      message: 'load-balancer-api-external: resolved host name a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:23:55Z"
    - latency: 5.367578ms
      message: 'load-balancer-api-external: tcp connection to a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:22:55Z"
    - latency: 8.483295ms
      message: 'load-balancer-api-external: resolved host name a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:22:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:50:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-53-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-53.ec2.internal
      uid: 0f180e43-3343-4d2c-b5ef-95e59c4cc98f
    resourceVersion: "55620"
    uid: 7245e00c-bcb5-4b0e-9393-1e7012e24ec2
  spec:
    sourcePod: network-check-source-989f8b8dc-lxgs9
    targetEndpoint: a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:56:55Z"
      message: 'load-balancer-api-internal: tcp connection to a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.901861ms
      message: 'load-balancer-api-internal: tcp connection to a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:26:55Z"
    - latency: 8.92656ms
      message: 'load-balancer-api-internal: resolved host name a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:26:55Z"
    - latency: 3.491222ms
      message: 'load-balancer-api-internal: tcp connection to a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:25:55Z"
    - latency: 10.044931ms
      message: 'load-balancer-api-internal: resolved host name a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:25:55Z"
    - latency: 4.81685ms
      message: 'load-balancer-api-internal: tcp connection to a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:24:55Z"
    - latency: 8.833276ms
      message: 'load-balancer-api-internal: resolved host name a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:24:55Z"
    - latency: 3.59096ms
      message: 'load-balancer-api-internal: tcp connection to a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:23:55Z"
    - latency: 8.471563ms
      message: 'load-balancer-api-internal: resolved host name a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:23:55Z"
    - latency: 5.356333ms
      message: 'load-balancer-api-internal: tcp connection to a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:22:55Z"
    - latency: 8.430109ms
      message: 'load-balancer-api-internal: resolved host name a627ca4ccd33443d7a2038d2d51ed17f-941f27fd690b701a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:22:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:50:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-53-to-network-check-target-ip-10-0-128-38
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-53.ec2.internal
      uid: 0f180e43-3343-4d2c-b5ef-95e59c4cc98f
    resourceVersion: "54629"
    uid: 4c6ea84a-bfcc-4343-b5cf-9a7d3aacd1ef
  spec:
    sourcePod: network-check-source-989f8b8dc-lxgs9
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:57:55Z"
      message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.332213ms
      message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:25:55Z"
    - latency: 2.393814ms
      message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:24:55Z"
    - latency: 2.552705ms
      message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:23:55Z"
    - latency: 2.603971ms
      message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:22:55Z"
    - latency: 2.553913ms
      message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:21:55Z"
    - latency: 2.500001ms
      message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:20:55Z"
    - latency: 2.491765ms
      message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:19:55Z"
    - latency: 2.79945ms
      message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:18:55Z"
    - latency: 2.256614ms
      message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:17:55Z"
    - latency: 2.398146ms
      message: 'network-check-target-ip-10-0-128-38: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:16:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:50:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-53-to-network-check-target-ip-10-0-134-52
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-53.ec2.internal
      uid: 0f180e43-3343-4d2c-b5ef-95e59c4cc98f
    resourceVersion: "54628"
    uid: 3a416c9a-46fc-4467-baef-5bb48f6118e6
  spec:
    sourcePod: network-check-source-989f8b8dc-lxgs9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:57:55Z"
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.328959ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:25:55Z"
    - latency: 2.10173ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:24:55Z"
    - latency: 2.300818ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:23:55Z"
    - latency: 2.275656ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:22:55Z"
    - latency: 2.21043ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:21:55Z"
    - latency: 2.493622ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:20:55Z"
    - latency: 2.535282ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:19:55Z"
    - latency: 2.451469ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:18:55Z"
    - latency: 2.142005ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:17:55Z"
    - latency: 2.095693ms
      message: 'network-check-target-ip-10-0-134-52: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:16:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:50:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-53-to-network-check-target-ip-10-0-140-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-53.ec2.internal
      uid: 0f180e43-3343-4d2c-b5ef-95e59c4cc98f
    resourceVersion: "54627"
    uid: db66c475-8463-4e73-b9f2-40bf07408bdf
  spec:
    sourcePod: network-check-source-989f8b8dc-lxgs9
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:57:55Z"
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.134628ms
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:25:55Z"
    - latency: 946.418µs
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:24:55Z"
    - latency: 980.191µs
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:23:55Z"
    - latency: 943.37µs
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:22:55Z"
    - latency: 801.8µs
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:21:55Z"
    - latency: 867.174µs
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:20:55Z"
    - latency: 984.532µs
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:19:55Z"
    - latency: 904.721µs
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:18:55Z"
    - latency: 789.729µs
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:17:55Z"
    - latency: 812.68µs
      message: 'network-check-target-ip-10-0-140-53: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:16:55Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:50:54Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-53-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-53.ec2.internal
      uid: 0f180e43-3343-4d2c-b5ef-95e59c4cc98f
    resourceVersion: "55618"
    uid: 12b787ec-2484-4dae-b180-db0aae8ed3e2
  spec:
    sourcePod: network-check-source-989f8b8dc-lxgs9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:56:55Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 778.188µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:26:55Z"
    - latency: 1.644881ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:26:55Z"
    - latency: 1.174779ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:25:55Z"
    - latency: 2.040167ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:25:55Z"
    - latency: 1.19612ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:24:55Z"
    - latency: 1.873497ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:24:55Z"
    - latency: 1.004803ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:23:55Z"
    - latency: 1.99553ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:23:55Z"
    - latency: 887.41µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:22:55Z"
    - latency: 2.05608ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:22:55Z"
kind: List
metadata:
  resourceVersion: ""