apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T19:32:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-144-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-144.ec2.internal
      uid: e469e28f-1918-4e3e-98a3-e3ddd275993b
    resourceVersion: "37339"
    uid: 71649403-852b-4a55-b4a4-dee807fd5805
  spec:
    sourcePod: network-check-source-8894fc9bd-lvq7b
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T19:39:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.007µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:21:36Z"
    - latency: 789.154µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:20:36Z"
    - latency: 958.954µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:19:36Z"
    - latency: 987.017µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:18:36Z"
    - latency: 1.067103ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:17:36Z"
    - latency: 970.986µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:16:36Z"
    - latency: 977.108µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:15:36Z"
    - latency: 1.607077ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:14:36Z"
    - latency: 973.242µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:13:36Z"
    - latency: 900.137µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:12:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T19:32:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-144-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-144.ec2.internal
      uid: e469e28f-1918-4e3e-98a3-e3ddd275993b
    resourceVersion: "36822"
    uid: 2aebf94a-8960-44f7-a76e-a28e7802e262
  spec:
    sourcePod: network-check-source-8894fc9bd-lvq7b
    targetEndpoint: a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T19:38:36Z"
      message: 'load-balancer-api-external: tcp connection to a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.277659ms
      message: 'load-balancer-api-external: tcp connection to a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:20:36Z"
    - latency: 7.042558ms
      message: 'load-balancer-api-external: resolved host name a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:20:36Z"
    - latency: 4.831827ms
      message: 'load-balancer-api-external: tcp connection to a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:19:36Z"
    - latency: 6.634971ms
      message: 'load-balancer-api-external: resolved host name a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:19:36Z"
    - latency: 4.494337ms
      message: 'load-balancer-api-external: tcp connection to a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:18:36Z"
    - latency: 6.201039ms
      message: 'load-balancer-api-external: resolved host name a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:18:36Z"
    - latency: 5.039592ms
      message: 'load-balancer-api-external: tcp connection to a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:17:36Z"
    - latency: 6.279185ms
      message: 'load-balancer-api-external: resolved host name a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:17:36Z"
    - latency: 3.342607ms
      message: 'load-balancer-api-external: tcp connection to a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:16:36Z"
    - latency: 6.309088ms
      message: 'load-balancer-api-external: resolved host name a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:16:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T19:32:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-144-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-144.ec2.internal
      uid: e469e28f-1918-4e3e-98a3-e3ddd275993b
    resourceVersion: "36823"
    uid: f9f2573a-b411-4856-8d2b-9f66e0afb9e4
  spec:
    sourcePod: network-check-source-8894fc9bd-lvq7b
    targetEndpoint: a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T19:38:36Z"
      message: 'load-balancer-api-internal: tcp connection to a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.249606ms
      message: 'load-balancer-api-internal: tcp connection to a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:20:36Z"
    - latency: 7.014054ms
      message: 'load-balancer-api-internal: resolved host name a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:20:36Z"
    - latency: 4.497361ms
      message: 'load-balancer-api-internal: tcp connection to a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:19:36Z"
    - latency: 6.598064ms
      message: 'load-balancer-api-internal: resolved host name a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:19:36Z"
    - latency: 4.476685ms
      message: 'load-balancer-api-internal: tcp connection to a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:18:36Z"
    - latency: 6.153631ms
      message: 'load-balancer-api-internal: resolved host name a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:18:36Z"
    - latency: 4.845998ms
      message: 'load-balancer-api-internal: tcp connection to a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:17:36Z"
    - latency: 6.223242ms
      message: 'load-balancer-api-internal: resolved host name a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:17:36Z"
    - latency: 3.064238ms
      message: 'load-balancer-api-internal: tcp connection to a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:16:36Z"
    - latency: 6.285473ms
      message: 'load-balancer-api-internal: resolved host name a72dac4f00a87439ba5ebcb0876b84f2-07dcf5a1ad76a9a3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:16:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T19:32:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-144-to-network-check-target-ip-10-0-134-231
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-144.ec2.internal
      uid: e469e28f-1918-4e3e-98a3-e3ddd275993b
    resourceVersion: "37336"
    uid: da314703-c57f-454d-a683-ad2964d33a47
  spec:
    sourcePod: network-check-source-8894fc9bd-lvq7b
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T19:39:36Z"
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.674263ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:21:36Z"
    - latency: 1.607463ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:20:36Z"
    - latency: 1.609021ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:19:36Z"
    - latency: 1.602318ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:18:36Z"
    - latency: 1.52005ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:17:36Z"
    - latency: 1.606945ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:16:36Z"
    - latency: 1.968023ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:15:36Z"
    - latency: 2.114299ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:14:36Z"
    - latency: 1.845653ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:13:36Z"
    - latency: 1.531324ms
      message: 'network-check-target-ip-10-0-134-231: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:12:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T19:32:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-144-to-network-check-target-ip-10-0-135-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-144.ec2.internal
      uid: e469e28f-1918-4e3e-98a3-e3ddd275993b
    resourceVersion: "37337"
    uid: d42c4482-2a9a-45dc-b331-81d4c665d5bd
  spec:
    sourcePod: network-check-source-8894fc9bd-lvq7b
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T19:39:36Z"
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.45607ms
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:21:36Z"
    - latency: 1.080008ms
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:20:36Z"
    - latency: 813.48µs
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:19:36Z"
    - latency: 773.086µs
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:18:36Z"
    - latency: 1.213347ms
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:17:36Z"
    - latency: 887.225µs
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:16:36Z"
    - latency: 779.405µs
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:15:36Z"
    - latency: 687.979µs
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:14:36Z"
    - latency: 1.233664ms
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:13:36Z"
    - latency: 783.121µs
      message: 'network-check-target-ip-10-0-135-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:12:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T19:32:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-144-to-network-check-target-ip-10-0-141-16
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-144.ec2.internal
      uid: e469e28f-1918-4e3e-98a3-e3ddd275993b
    resourceVersion: "37338"
    uid: 2c1ed8a7-d0f1-4578-a227-6fd5e8455a56
  spec:
    sourcePod: network-check-source-8894fc9bd-lvq7b
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T19:39:36Z"
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.015438ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:21:36Z"
    - latency: 2.010538ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:20:36Z"
    - latency: 2.034685ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:19:36Z"
    - latency: 2.111729ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:18:36Z"
    - latency: 2.13189ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:17:36Z"
    - latency: 2.039747ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:16:36Z"
    - latency: 1.920782ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:15:36Z"
    - latency: 2.0618ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:14:36Z"
    - latency: 2.039495ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:13:36Z"
    - latency: 2.200929ms
      message: 'network-check-target-ip-10-0-141-16: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:12:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T19:32:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-135-144-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-135-144.ec2.internal
      uid: e469e28f-1918-4e3e-98a3-e3ddd275993b
    resourceVersion: "36821"
    uid: 6be0b06b-f728-4ae1-acf3-f3ca936bf557
  spec:
    sourcePod: network-check-source-8894fc9bd-lvq7b
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T19:38:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 875.009µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:20:36Z"
    - latency: 2.086114ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:20:36Z"
    - latency: 1.137664ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:19:36Z"
    - latency: 1.717425ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:19:36Z"
    - latency: 814.618µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:18:36Z"
    - latency: 1.556296ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:18:36Z"
    - latency: 775.429µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:17:36Z"
    - latency: 1.512367ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:17:36Z"
    - latency: 806.067µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:16:36Z"
    - latency: 1.518999ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:16:36Z"
kind: List
metadata:
  resourceVersion: ""