apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T12:54:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-85-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-85.ec2.internal
      uid: d47cc9f1-dfbf-4911-8650-3646b866b6eb
    resourceVersion: "44865"
    uid: 5a34c1b3-f3f1-45b3-8473-7ceb9eb6f1ed
  spec:
    sourcePod: network-check-source-dbd9cf844-67sx9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T13:01:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.019274ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:22:43Z"
    - latency: 946.809µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:21:43Z"
    - latency: 847.747µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:20:43Z"
    - latency: 897.681µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:19:43Z"
    - latency: 1.12343ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:18:43Z"
    - latency: 1.361388ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:17:43Z"
    - latency: 1.077117ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:16:43Z"
    - latency: 1.336735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:15:43Z"
    - latency: 1.153639ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:14:43Z"
    - latency: 1.014176ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:13:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T12:54:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-85-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-85.ec2.internal
      uid: d47cc9f1-dfbf-4911-8650-3646b866b6eb
    resourceVersion: "46901"
    uid: df12d055-2297-4478-8e67-e2ac701d5d50
  spec:
    sourcePod: network-check-source-dbd9cf844-67sx9
    targetEndpoint: a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T13:00:43Z"
      message: 'load-balancer-api-external: tcp connection to a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.410798ms
      message: 'load-balancer-api-external: tcp connection to a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:24:43Z"
    - latency: 8.11629ms
      message: 'load-balancer-api-external: resolved host name a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:24:43Z"
    - latency: 7.492292ms
      message: 'load-balancer-api-external: tcp connection to a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:23:43Z"
    - latency: 8.330302ms
      message: 'load-balancer-api-external: resolved host name a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:23:43Z"
    - latency: 4.355771ms
      message: 'load-balancer-api-external: tcp connection to a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:22:43Z"
    - latency: 8.371058ms
      message: 'load-balancer-api-external: resolved host name a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:22:43Z"
    - latency: 4.794334ms
      message: 'load-balancer-api-external: tcp connection to a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:21:43Z"
    - latency: 7.950539ms
      message: 'load-balancer-api-external: resolved host name a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:21:43Z"
    - latency: 4.90155ms
      message: 'load-balancer-api-external: tcp connection to a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:20:43Z"
    - latency: 7.915111ms
      message: 'load-balancer-api-external: resolved host name a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:20:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T12:54:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-85-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-85.ec2.internal
      uid: d47cc9f1-dfbf-4911-8650-3646b866b6eb
    resourceVersion: "46900"
    uid: 97d5dfbb-a960-445c-86e0-5a93f9620c71
  spec:
    sourcePod: network-check-source-dbd9cf844-67sx9
    targetEndpoint: a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T13:00:43Z"
      message: 'load-balancer-api-internal: tcp connection to a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.381787ms
      message: 'load-balancer-api-internal: tcp connection to a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:24:43Z"
    - latency: 8.019726ms
      message: 'load-balancer-api-internal: resolved host name a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:24:43Z"
    - latency: 6.566787ms
      message: 'load-balancer-api-internal: tcp connection to a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:23:43Z"
    - latency: 8.300939ms
      message: 'load-balancer-api-internal: resolved host name a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:23:43Z"
    - latency: 4.107667ms
      message: 'load-balancer-api-internal: tcp connection to a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:22:43Z"
    - latency: 8.260381ms
      message: 'load-balancer-api-internal: resolved host name a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:22:43Z"
    - latency: 4.732228ms
      message: 'load-balancer-api-internal: tcp connection to a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:21:43Z"
    - latency: 8.02377ms
      message: 'load-balancer-api-internal: resolved host name a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:21:43Z"
    - latency: 4.954684ms
      message: 'load-balancer-api-internal: tcp connection to a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:20:43Z"
    - latency: 7.80581ms
      message: 'load-balancer-api-internal: resolved host name a5913e35a7a1c43a2beb35895071119a-3d207a230a3b3edd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:20:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T12:54:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-85-to-network-check-target-ip-10-0-130-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-85.ec2.internal
      uid: d47cc9f1-dfbf-4911-8650-3646b866b6eb
    resourceVersion: "44862"
    uid: cb0c1f8c-0b06-4d98-beef-09daff4f5ebc
  spec:
    sourcePod: network-check-source-dbd9cf844-67sx9
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T13:01:43Z"
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.09392ms
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:22:43Z"
    - latency: 1.044396ms
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:21:43Z"
    - latency: 972.932µs
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:20:43Z"
    - latency: 1.057916ms
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:19:43Z"
    - latency: 953.473µs
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:18:43Z"
    - latency: 1.862826ms
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:17:43Z"
    - latency: 1.407204ms
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:16:43Z"
    - latency: 1.268626ms
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:15:43Z"
    - latency: 1.715646ms
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:14:43Z"
    - latency: 996.942µs
      message: 'network-check-target-ip-10-0-130-85: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:13:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T12:54:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-85-to-network-check-target-ip-10-0-140-124
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-85.ec2.internal
      uid: d47cc9f1-dfbf-4911-8650-3646b866b6eb
    resourceVersion: "44863"
    uid: b7265ae7-9811-4fe4-985f-06b805fdaac6
  spec:
    sourcePod: network-check-source-dbd9cf844-67sx9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T13:01:43Z"
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.173363ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:22:43Z"
    - latency: 2.245994ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:21:43Z"
    - latency: 2.247112ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:20:43Z"
    - latency: 2.108912ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:19:43Z"
    - latency: 2.215956ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:18:43Z"
    - latency: 2.372596ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:17:43Z"
    - latency: 2.293457ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:16:43Z"
    - latency: 2.08867ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:15:43Z"
    - latency: 2.377286ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:14:43Z"
    - latency: 2.323743ms
      message: 'network-check-target-ip-10-0-140-124: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:13:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T12:54:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-85-to-network-check-target-ip-10-0-140-135
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-85.ec2.internal
      uid: d47cc9f1-dfbf-4911-8650-3646b866b6eb
    resourceVersion: "44864"
    uid: 7ca62bb5-b2cc-45c8-95c2-cf34d4c6bdc3
  spec:
    sourcePod: network-check-source-dbd9cf844-67sx9
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T13:01:43Z"
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.474588ms
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:22:43Z"
    - latency: 2.276502ms
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:21:43Z"
    - latency: 2.261381ms
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:20:43Z"
    - latency: 1.970476ms
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:19:43Z"
    - latency: 2.433544ms
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:18:43Z"
    - latency: 2.960474ms
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:17:43Z"
    - latency: 1.991873ms
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:16:43Z"
    - latency: 2.393306ms
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:15:43Z"
    - latency: 2.308707ms
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:14:43Z"
    - latency: 2.339165ms
      message: 'network-check-target-ip-10-0-140-135: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:13:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-10T12:54:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-85-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-85.ec2.internal
      uid: d47cc9f1-dfbf-4911-8650-3646b866b6eb
    resourceVersion: "46899"
    uid: a3793e37-a481-4fb4-b228-ae30de1435b9
  spec:
    sourcePod: network-check-source-dbd9cf844-67sx9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-10T13:00:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 806.994µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:24:43Z"
    - latency: 1.736944ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:24:43Z"
    - latency: 914.304µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:23:43Z"
    - latency: 1.764048ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:23:43Z"
    - latency: 965.107µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:22:43Z"
    - latency: 1.892076ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:22:43Z"
    - latency: 782.134µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:21:43Z"
    - latency: 1.66562ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:21:43Z"
    - latency: 772.727µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-10T13:20:43Z"
    - latency: 1.623452ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-10T13:20:43Z"
kind: List
metadata:
  resourceVersion: ""