apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T12:27:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-43-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-43.ec2.internal
      uid: 08b9251b-6806-4997-9a77-2e6f91c7c4f8
    resourceVersion: "53521"
    uid: a7dd8d1e-89f4-46ab-99cc-64435b8b90aa
  spec:
    sourcePod: network-check-source-989f8b8dc-k2vc6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T12:34:42Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 972.489µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:02:42Z"
    - latency: 1.290033ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:01:42Z"
    - latency: 882.738µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:00:42Z"
    - latency: 1.023952ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:59:42Z"
    - latency: 886.95µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:58:42Z"
    - latency: 908.56µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:57:42Z"
    - latency: 1.248098ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:56:42Z"
    - latency: 908.952µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:55:42Z"
    - latency: 1.024914ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:54:42Z"
    - latency: 1.123824ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:53:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T12:27:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-43-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-43.ec2.internal
      uid: 08b9251b-6806-4997-9a77-2e6f91c7c4f8
    resourceVersion: "54477"
    uid: 65bc1a3c-a74a-4ec4-8824-8f2147eb3744
  spec:
    sourcePod: network-check-source-989f8b8dc-k2vc6
    targetEndpoint: a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T12:33:42Z"
      message: 'load-balancer-api-external: tcp connection to a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.585729ms
      message: 'load-balancer-api-external: tcp connection to a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:03:42Z"
    - latency: 7.079052ms
      message: 'load-balancer-api-external: resolved host name a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:03:42Z"
    - latency: 5.012526ms
      message: 'load-balancer-api-external: tcp connection to a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:02:42Z"
    - latency: 7.075769ms
      message: 'load-balancer-api-external: resolved host name a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:02:42Z"
    - latency: 5.476008ms
      message: 'load-balancer-api-external: tcp connection to a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:01:42Z"
    - latency: 8.227148ms
      message: 'load-balancer-api-external: resolved host name a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:01:42Z"
    - latency: 4.885577ms
      message: 'load-balancer-api-external: tcp connection to a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:00:42Z"
    - latency: 10.800732ms
      message: 'load-balancer-api-external: resolved host name a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:00:42Z"
    - latency: 4.587929ms
      message: 'load-balancer-api-external: tcp connection to a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:59:42Z"
    - latency: 6.468029ms
      message: 'load-balancer-api-external: resolved host name a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T12:59:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T12:27:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-43-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-43.ec2.internal
      uid: 08b9251b-6806-4997-9a77-2e6f91c7c4f8
    resourceVersion: "54476"
    uid: a4c26c6d-e03e-4571-a4b3-ed4adc378bb1
  spec:
    sourcePod: network-check-source-989f8b8dc-k2vc6
    targetEndpoint: a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T12:33:42Z"
      message: 'load-balancer-api-internal: tcp connection to a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.628624ms
      message: 'load-balancer-api-internal: tcp connection to a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:03:42Z"
    - latency: 7.003079ms
      message: 'load-balancer-api-internal: resolved host name a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:03:42Z"
    - latency: 5.02916ms
      message: 'load-balancer-api-internal: tcp connection to a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:02:42Z"
    - latency: 6.959625ms
      message: 'load-balancer-api-internal: resolved host name a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:02:42Z"
    - latency: 5.456152ms
      message: 'load-balancer-api-internal: tcp connection to a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:01:42Z"
    - latency: 8.307095ms
      message: 'load-balancer-api-internal: resolved host name a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:01:42Z"
    - latency: 4.317199ms
      message: 'load-balancer-api-internal: tcp connection to a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:00:42Z"
    - latency: 10.885259ms
      message: 'load-balancer-api-internal: resolved host name a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:00:42Z"
    - latency: 4.601109ms
      message: 'load-balancer-api-internal: tcp connection to a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:59:42Z"
    - latency: 6.41332ms
      message: 'load-balancer-api-internal: resolved host name a5f1182d4552047c68b36a22b7e15b3c-dd8c04a765c803e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T12:59:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T12:27:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-43-to-network-check-target-ip-10-0-140-237
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-43.ec2.internal
      uid: 08b9251b-6806-4997-9a77-2e6f91c7c4f8
    resourceVersion: "53520"
    uid: aff2c7f7-c776-4989-bdae-36979bb1d35f
  spec:
    sourcePod: network-check-source-989f8b8dc-k2vc6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T12:34:42Z"
      message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.284025ms
      message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:02:42Z"
    - latency: 2.634782ms
      message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:01:42Z"
    - latency: 2.564477ms
      message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:00:42Z"
    - latency: 2.158398ms
      message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:59:42Z"
    - latency: 2.053667ms
      message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:58:42Z"
    - latency: 2.30846ms
      message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:57:42Z"
    - latency: 2.442837ms
      message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:56:42Z"
    - latency: 2.605095ms
      message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:55:42Z"
    - latency: 2.429362ms
      message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:54:42Z"
    - latency: 2.308918ms
      message: 'network-check-target-ip-10-0-140-237: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:53:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T12:27:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-43-to-network-check-target-ip-10-0-140-238
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-43.ec2.internal
      uid: 08b9251b-6806-4997-9a77-2e6f91c7c4f8
    resourceVersion: "53519"
    uid: 99be7b22-a7da-475b-be73-1132f5de62f5
  spec:
    sourcePod: network-check-source-989f8b8dc-k2vc6
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T12:34:42Z"
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.198305ms
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:02:42Z"
    - latency: 2.696217ms
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:01:42Z"
    - latency: 2.451005ms
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:00:42Z"
    - latency: 2.34216ms
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:59:42Z"
    - latency: 2.067629ms
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:58:42Z"
    - latency: 1.965526ms
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:57:42Z"
    - latency: 2.209445ms
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:56:42Z"
    - latency: 2.367459ms
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:55:42Z"
    - latency: 2.404502ms
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:54:42Z"
    - latency: 2.125455ms
      message: 'network-check-target-ip-10-0-140-238: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:53:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T12:27:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-43-to-network-check-target-ip-10-0-142-43
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-43.ec2.internal
      uid: 08b9251b-6806-4997-9a77-2e6f91c7c4f8
    resourceVersion: "53518"
    uid: 88276dc7-7e2f-4fb3-9326-69b9376e718e
  spec:
    sourcePod: network-check-source-989f8b8dc-k2vc6
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T12:34:42Z"
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.270528ms
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:02:42Z"
    - latency: 1.030562ms
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:01:42Z"
    - latency: 1.015717ms
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:00:42Z"
    - latency: 896.359µs
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:59:42Z"
    - latency: 771.459µs
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:58:42Z"
    - latency: 839.999µs
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:57:42Z"
    - latency: 921.359µs
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:56:42Z"
    - latency: 859.82µs
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:55:42Z"
    - latency: 1.265273ms
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:54:42Z"
    - latency: 1.229603ms
      message: 'network-check-target-ip-10-0-142-43: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:53:42Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T12:27:40Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-43-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-43.ec2.internal
      uid: 08b9251b-6806-4997-9a77-2e6f91c7c4f8
    resourceVersion: "54475"
    uid: 3a8e3cd6-08d7-4da4-aed9-ea9b68278a67
  spec:
    sourcePod: network-check-source-989f8b8dc-k2vc6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T12:33:42Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 813.031µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:03:42Z"
    - latency: 1.76713ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:03:42Z"
    - latency: 1.210023ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:02:42Z"
    - latency: 1.586208ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:02:42Z"
    - latency: 968.958µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:01:42Z"
    - latency: 1.954927ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:01:42Z"
    - latency: 850.372µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T13:00:42Z"
    - latency: 1.786827ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T13:00:42Z"
    - latency: 821.468µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T12:59:42Z"
    - latency: 1.779635ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T12:59:42Z"
kind: List
metadata:
  resourceVersion: ""