apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-75-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-75.ec2.internal
      uid: 529ac253-b2c8-4e93-af05-5135a3910ac0
    resourceVersion: "54251"
    uid: 62dd0aa2-76a8-49aa-acf5-4e666cc967cd
  spec:
    sourcePod: network-check-source-989f8b8dc-hblrp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:07:49Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.041672ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:35:49Z"
    - latency: 1.116965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:34:49Z"
    - latency: 1.450171ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:33:49Z"
    - latency: 902.862µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:32:49Z"
    - latency: 1.056944ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:31:49Z"
    - latency: 819.119µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:49Z"
    - latency: 1.256216ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:49Z"
    - latency: 1.671696ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:49Z"
    - latency: 816.04µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:49Z"
    - latency: 1.168032ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:26:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-75-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-75.ec2.internal
      uid: 529ac253-b2c8-4e93-af05-5135a3910ac0
    resourceVersion: "55216"
    uid: a8c10a65-1174-42e3-ade6-6d3e6df5cf77
  spec:
    sourcePod: network-check-source-989f8b8dc-hblrp
    targetEndpoint: a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:06:49Z"
      message: 'load-balancer-api-external: tcp connection to a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.683603ms
      message: 'load-balancer-api-external: tcp connection to a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:36:49Z"
    - latency: 8.87413ms
      message: 'load-balancer-api-external: resolved host name a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:36:49Z"
    - latency: 3.754156ms
      message: 'load-balancer-api-external: tcp connection to a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:35:49Z"
    - latency: 9.633269ms
      message: 'load-balancer-api-external: resolved host name a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:35:49Z"
    - latency: 5.603857ms
      message: 'load-balancer-api-external: tcp connection to a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:34:49Z"
    - latency: 8.888144ms
      message: 'load-balancer-api-external: resolved host name a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:34:49Z"
    - latency: 4.009458ms
      message: 'load-balancer-api-external: tcp connection to a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:33:49Z"
    - latency: 9.516545ms
      message: 'load-balancer-api-external: resolved host name a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:33:49Z"
    - latency: 5.075901ms
      message: 'load-balancer-api-external: tcp connection to a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:32:49Z"
    - latency: 8.774082ms
      message: 'load-balancer-api-external: resolved host name a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:32:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-75-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-75.ec2.internal
      uid: 529ac253-b2c8-4e93-af05-5135a3910ac0
    resourceVersion: "55215"
    uid: 57ef05aa-91b9-465a-aa88-e10ea9819f4f
  spec:
    sourcePod: network-check-source-989f8b8dc-hblrp
    targetEndpoint: a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:06:49Z"
      message: 'load-balancer-api-internal: tcp connection to a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.700774ms
      message: 'load-balancer-api-internal: tcp connection to a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:36:49Z"
    - latency: 8.848963ms
      message: 'load-balancer-api-internal: resolved host name a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:36:49Z"
    - latency: 3.715069ms
      message: 'load-balancer-api-internal: tcp connection to a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:35:49Z"
    - latency: 9.603731ms
      message: 'load-balancer-api-internal: resolved host name a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:35:49Z"
    - latency: 5.675794ms
      message: 'load-balancer-api-internal: tcp connection to a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:34:49Z"
    - latency: 8.841579ms
      message: 'load-balancer-api-internal: resolved host name a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:34:49Z"
    - latency: 4.493057ms
      message: 'load-balancer-api-internal: tcp connection to a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:33:49Z"
    - latency: 9.455298ms
      message: 'load-balancer-api-internal: resolved host name a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:33:49Z"
    - latency: 4.995015ms
      message: 'load-balancer-api-internal: tcp connection to a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:32:49Z"
    - latency: 8.641615ms
      message: 'load-balancer-api-internal: resolved host name a4a901b97063f46b5820d096d0660ceb-02342cde4f2e94de.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:32:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-75-to-network-check-target-ip-10-0-132-75
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-75.ec2.internal
      uid: 529ac253-b2c8-4e93-af05-5135a3910ac0
    resourceVersion: "54249"
    uid: b5c45db2-40a2-4afd-9f02-b3ef14972fde
  spec:
    sourcePod: network-check-source-989f8b8dc-hblrp
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:07:49Z"
      message: 'network-check-target-ip-10-0-132-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.198534ms
      message: 'network-check-target-ip-10-0-132-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:35:49Z"
    - latency: 1.314799ms
      message: 'network-check-target-ip-10-0-132-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:34:49Z"
    - latency: 1.716857ms
      message: 'network-check-target-ip-10-0-132-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:33:49Z"
    - latency: 874.859µs
      message: 'network-check-target-ip-10-0-132-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:32:49Z"
    - latency: 774.709µs
      message: 'network-check-target-ip-10-0-132-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:31:49Z"
    - latency: 749.024µs
      message: 'network-check-target-ip-10-0-132-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:49Z"
    - latency: 1.553418ms
      message: 'network-check-target-ip-10-0-132-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:49Z"
    - latency: 1.275878ms
      message: 'network-check-target-ip-10-0-132-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:49Z"
    - latency: 1.500717ms
      message: 'network-check-target-ip-10-0-132-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:49Z"
    - latency: 931.556µs
      message: 'network-check-target-ip-10-0-132-75: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:26:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-75-to-network-check-target-ip-10-0-136-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-75.ec2.internal
      uid: 529ac253-b2c8-4e93-af05-5135a3910ac0
    resourceVersion: "54250"
    uid: b00002ca-8f00-48e0-a6ed-1cdfa896677e
  spec:
    sourcePod: network-check-source-989f8b8dc-hblrp
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:07:49Z"
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.987178ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:35:49Z"
    - latency: 1.789748ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:34:49Z"
    - latency: 2.277079ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:33:49Z"
    - latency: 1.848907ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:32:49Z"
    - latency: 1.880747ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:31:49Z"
    - latency: 1.66301ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:49Z"
    - latency: 2.150222ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:49Z"
    - latency: 2.048859ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:49Z"
    - latency: 1.76997ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:49Z"
    - latency: 1.94725ms
      message: 'network-check-target-ip-10-0-136-8: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:26:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-75-to-network-check-target-ip-10-0-142-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-75.ec2.internal
      uid: 529ac253-b2c8-4e93-af05-5135a3910ac0
    resourceVersion: "54248"
    uid: d49f397e-e980-45ca-aef3-f981cd452e0e
  spec:
    sourcePod: network-check-source-989f8b8dc-hblrp
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:07:49Z"
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.961851ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:35:49Z"
    - latency: 2.104965ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:34:49Z"
    - latency: 2.458548ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:33:49Z"
    - latency: 2.096687ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:32:49Z"
    - latency: 2.054489ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:31:49Z"
    - latency: 2.121874ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:30:49Z"
    - latency: 2.403435ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:29:49Z"
    - latency: 2.265203ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:28:49Z"
    - latency: 2.171831ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:27:49Z"
    - latency: 2.31953ms
      message: 'network-check-target-ip-10-0-142-101: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:26:49Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-02T20:00:48Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-75-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-75.ec2.internal
      uid: 529ac253-b2c8-4e93-af05-5135a3910ac0
    resourceVersion: "55214"
    uid: 20823228-5b29-4ebe-82e1-d4f7ba7e6ea1
  spec:
    sourcePod: network-check-source-989f8b8dc-hblrp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-02T20:06:49Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.157223ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:36:49Z"
    - latency: 1.762985ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:36:49Z"
    - latency: 968.59µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:35:49Z"
    - latency: 2.240383ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:35:49Z"
    - latency: 968.781µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:34:49Z"
    - latency: 1.966154ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:34:49Z"
    - latency: 1.180627ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:33:49Z"
    - latency: 1.866256ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:33:49Z"
    - latency: 1.040848ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-02T20:32:49Z"
    - latency: 1.76863ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-02T20:32:49Z"
kind: List
metadata:
  resourceVersion: ""