apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T01:01:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-146-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-146.ec2.internal
      uid: 98c08567-dbce-410e-9259-bf93279b0fc3
    resourceVersion: "44866"
    uid: 9a78c058-3d4f-48b3-91f1-224799cef5e2
  spec:
    sourcePod: network-check-source-6947749cfc-pcd4p
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T01:08:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.09811ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:29:47Z"
    - latency: 1.005878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:28:47Z"
    - latency: 910.161µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:27:47Z"
    - latency: 1.139277ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:26:47Z"
    - latency: 1.093014ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:25:47Z"
    - latency: 1.153375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:24:47Z"
    - latency: 953.309µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:23:47Z"
    - latency: 1.231277ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:22:47Z"
    - latency: 958.786µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:21:47Z"
    - latency: 829.644µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:20:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T01:01:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-146-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-146.ec2.internal
      uid: 98c08567-dbce-410e-9259-bf93279b0fc3
    resourceVersion: "46896"
    uid: bd3fe1c2-6af9-4337-a60c-af62a4e6d0c5
  spec:
    sourcePod: network-check-source-6947749cfc-pcd4p
    targetEndpoint: ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T01:07:47Z"
      message: 'load-balancer-api-external: tcp connection to ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.745022ms
      message: 'load-balancer-api-external: tcp connection to ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:31:47Z"
    - latency: 7.03892ms
      message: 'load-balancer-api-external: resolved host name ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:31:47Z"
    - latency: 5.594576ms
      message: 'load-balancer-api-external: tcp connection to ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:30:47Z"
    - latency: 8.0872ms
      message: 'load-balancer-api-external: resolved host name ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:30:47Z"
    - latency: 5.035804ms
      message: 'load-balancer-api-external: tcp connection to ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:29:47Z"
    - latency: 7.999426ms
      message: 'load-balancer-api-external: resolved host name ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:29:47Z"
    - latency: 4.565356ms
      message: 'load-balancer-api-external: tcp connection to ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:28:47Z"
    - latency: 7.253661ms
      message: 'load-balancer-api-external: resolved host name ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:28:47Z"
    - latency: 5.035246ms
      message: 'load-balancer-api-external: tcp connection to ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:27:47Z"
    - latency: 6.998592ms
      message: 'load-balancer-api-external: resolved host name ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:27:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T01:01:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-146-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-146.ec2.internal
      uid: 98c08567-dbce-410e-9259-bf93279b0fc3
    resourceVersion: "46897"
    uid: 60d0ca6f-5b84-4c4f-adac-d4cea6a8a438
  spec:
    sourcePod: network-check-source-6947749cfc-pcd4p
    targetEndpoint: ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T01:07:47Z"
      message: 'load-balancer-api-internal: tcp connection to ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.614304ms
      message: 'load-balancer-api-internal: tcp connection to ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:31:47Z"
    - latency: 7.11902ms
      message: 'load-balancer-api-internal: resolved host name ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:31:47Z"
    - latency: 5.248592ms
      message: 'load-balancer-api-internal: tcp connection to ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:30:47Z"
    - latency: 8.116944ms
      message: 'load-balancer-api-internal: resolved host name ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:30:47Z"
    - latency: 3.892781ms
      message: 'load-balancer-api-internal: tcp connection to ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:29:47Z"
    - latency: 8.043453ms
      message: 'load-balancer-api-internal: resolved host name ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:29:47Z"
    - latency: 3.959735ms
      message: 'load-balancer-api-internal: tcp connection to ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:28:47Z"
    - latency: 7.199782ms
      message: 'load-balancer-api-internal: resolved host name ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:28:47Z"
    - latency: 5.612031ms
      message: 'load-balancer-api-internal: tcp connection to ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:27:47Z"
    - latency: 6.968198ms
      message: 'load-balancer-api-internal: resolved host name ac3551c8e462f448a9fa72918070fddf-4b29a514b45ff104.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:27:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T01:01:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-146-to-network-check-target-ip-10-0-129-42
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-146.ec2.internal
      uid: 98c08567-dbce-410e-9259-bf93279b0fc3
    resourceVersion: "44865"
    uid: 9aa54fe4-401f-43d1-9e7d-6ab7d0aaf587
  spec:
    sourcePod: network-check-source-6947749cfc-pcd4p
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T01:08:47Z"
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.459994ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:29:47Z"
    - latency: 2.184309ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:28:47Z"
    - latency: 2.567943ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:27:47Z"
    - latency: 2.140156ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:26:47Z"
    - latency: 2.485678ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:25:47Z"
    - latency: 2.326195ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:24:47Z"
    - latency: 2.560439ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:23:47Z"
    - latency: 2.392649ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:22:47Z"
    - latency: 2.385369ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:21:47Z"
    - latency: 1.9945ms
      message: 'network-check-target-ip-10-0-129-42: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:20:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T01:01:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-146-to-network-check-target-ip-10-0-132-30
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-146.ec2.internal
      uid: 98c08567-dbce-410e-9259-bf93279b0fc3
    resourceVersion: "44864"
    uid: 1670438b-c25e-4aa7-81de-857ba4e6dbea
  spec:
    sourcePod: network-check-source-6947749cfc-pcd4p
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T01:08:47Z"
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.460608ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:29:47Z"
    - latency: 2.367753ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:28:47Z"
    - latency: 2.470977ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:27:47Z"
    - latency: 2.164479ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:26:47Z"
    - latency: 1.903755ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:25:47Z"
    - latency: 2.541128ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:24:47Z"
    - latency: 2.329535ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:23:47Z"
    - latency: 2.454425ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:22:47Z"
    - latency: 2.149248ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:21:47Z"
    - latency: 2.163081ms
      message: 'network-check-target-ip-10-0-132-30: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:20:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T01:01:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-146-to-network-check-target-ip-10-0-136-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-146.ec2.internal
      uid: 98c08567-dbce-410e-9259-bf93279b0fc3
    resourceVersion: "44863"
    uid: 86795970-292e-4a91-95c5-af8b0406a703
  spec:
    sourcePod: network-check-source-6947749cfc-pcd4p
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T01:08:47Z"
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 970.166µs
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:29:47Z"
    - latency: 1.255469ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:28:47Z"
    - latency: 973.462µs
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:27:47Z"
    - latency: 1.269312ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:26:47Z"
    - latency: 933.395µs
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:25:47Z"
    - latency: 878.697µs
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:24:47Z"
    - latency: 1.618911ms
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:23:47Z"
    - latency: 969.867µs
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:22:47Z"
    - latency: 874.041µs
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:21:47Z"
    - latency: 964.203µs
      message: 'network-check-target-ip-10-0-136-146: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:20:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T01:01:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-146-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-146.ec2.internal
      uid: 98c08567-dbce-410e-9259-bf93279b0fc3
    resourceVersion: "46895"
    uid: c7a1a80c-d7c1-4e8f-84af-e438369c11da
  spec:
    sourcePod: network-check-source-6947749cfc-pcd4p
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T01:07:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.127587ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:31:47Z"
    - latency: 1.974871ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:31:47Z"
    - latency: 1.162041ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:30:47Z"
    - latency: 1.86518ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:30:47Z"
    - latency: 1.226281ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:29:47Z"
    - latency: 1.891912ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:29:47Z"
    - latency: 1.062896ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:28:47Z"
    - latency: 1.897303ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:28:47Z"
    - latency: 1.062955ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T01:27:47Z"
    - latency: 1.733606ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T01:27:47Z"
kind: List
metadata:
  resourceVersion: ""