apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:12:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-160-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-160.ec2.internal
      uid: bed5946a-e1ed-4173-bb3e-5b0501210409
    resourceVersion: "51333"
    uid: 256e88a7-dc59-4bbf-b3ba-86359b160a12
  spec:
    sourcePod: network-check-source-869dcfcdcd-r97s6
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:20:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.367739ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:48:00Z"
    - latency: 1.09409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:47:00Z"
    - latency: 1.116606ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:46:00Z"
    - latency: 5.498311ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:45:00Z"
    - latency: 1.131058ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:44:00Z"
    - latency: 982.598µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:43:00Z"
    - latency: 962.201µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:42:00Z"
    - latency: 905.012µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:41:00Z"
    - latency: 929.488µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:40:00Z"
    - latency: 1.112686ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:39:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:12:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-160-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-160.ec2.internal
      uid: bed5946a-e1ed-4173-bb3e-5b0501210409
    resourceVersion: "52277"
    uid: a4c1175a-f8ab-4f43-b5b3-7cc53218cb17
  spec:
    sourcePod: network-check-source-869dcfcdcd-r97s6
    targetEndpoint: a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:19:00Z"
      message: 'load-balancer-api-external: tcp connection to a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.267668ms
      message: 'load-balancer-api-external: tcp connection to a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:49:00Z"
    - latency: 11.693858ms
      message: 'load-balancer-api-external: resolved host name a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:49:00Z"
    - latency: 4.107657ms
      message: 'load-balancer-api-external: tcp connection to a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:48:00Z"
    - latency: 7.16ms
      message: 'load-balancer-api-external: resolved host name a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:48:00Z"
    - latency: 10.159214ms
      message: 'load-balancer-api-external: tcp connection to a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:47:00Z"
    - latency: 6.724425ms
      message: 'load-balancer-api-external: resolved host name a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:47:00Z"
    - latency: 4.370298ms
      message: 'load-balancer-api-external: tcp connection to a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:46:00Z"
    - latency: 7.011278ms
      message: 'load-balancer-api-external: resolved host name a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:46:00Z"
    - latency: 12.664864ms
      message: 'load-balancer-api-external: tcp connection to a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:45:00Z"
    - latency: 27.927157ms
      message: 'load-balancer-api-external: resolved host name a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:45:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:12:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-160-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-160.ec2.internal
      uid: bed5946a-e1ed-4173-bb3e-5b0501210409
    resourceVersion: "52278"
    uid: 08cecbf5-9962-4e99-8ef8-250477b94776
  spec:
    sourcePod: network-check-source-869dcfcdcd-r97s6
    targetEndpoint: a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:19:00Z"
      message: 'load-balancer-api-internal: tcp connection to a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.017212ms
      message: 'load-balancer-api-internal: tcp connection to a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:49:00Z"
    - latency: 11.595276ms
      message: 'load-balancer-api-internal: resolved host name a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:49:00Z"
    - latency: 3.812551ms
      message: 'load-balancer-api-internal: tcp connection to a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:48:00Z"
    - latency: 7.202479ms
      message: 'load-balancer-api-internal: resolved host name a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:48:00Z"
    - latency: 12.788775ms
      message: 'load-balancer-api-internal: tcp connection to a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:47:00Z"
    - latency: 6.747681ms
      message: 'load-balancer-api-internal: resolved host name a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:47:00Z"
    - latency: 3.636615ms
      message: 'load-balancer-api-internal: tcp connection to a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:46:00Z"
    - latency: 7.026411ms
      message: 'load-balancer-api-internal: resolved host name a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:46:00Z"
    - latency: 12.047487ms
      message: 'load-balancer-api-internal: tcp connection to a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:45:00Z"
    - latency: 28.775339ms
      message: 'load-balancer-api-internal: resolved host name a14f8b3648659458180b92f71dc23752-b3f21f36e82452cd.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:45:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:12:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-160-to-network-check-target-ip-10-0-139-22
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-160.ec2.internal
      uid: bed5946a-e1ed-4173-bb3e-5b0501210409
    resourceVersion: "51332"
    uid: 545705b2-f057-4a01-86af-ff854a105cff
  spec:
    sourcePod: network-check-source-869dcfcdcd-r97s6
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:20:00Z"
      message: 'network-check-target-ip-10-0-139-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.502898ms
      message: 'network-check-target-ip-10-0-139-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:48:00Z"
    - latency: 2.710111ms
      message: 'network-check-target-ip-10-0-139-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:47:00Z"
    - latency: 2.324592ms
      message: 'network-check-target-ip-10-0-139-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:46:00Z"
    - latency: 3.870203ms
      message: 'network-check-target-ip-10-0-139-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:45:00Z"
    - latency: 2.50652ms
      message: 'network-check-target-ip-10-0-139-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:44:00Z"
    - latency: 2.118364ms
      message: 'network-check-target-ip-10-0-139-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:43:00Z"
    - latency: 2.269786ms
      message: 'network-check-target-ip-10-0-139-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:42:00Z"
    - latency: 2.048872ms
      message: 'network-check-target-ip-10-0-139-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:41:00Z"
    - latency: 2.742143ms
      message: 'network-check-target-ip-10-0-139-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:40:00Z"
    - latency: 2.537554ms
      message: 'network-check-target-ip-10-0-139-22: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:39:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:12:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-160-to-network-check-target-ip-10-0-140-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-160.ec2.internal
      uid: bed5946a-e1ed-4173-bb3e-5b0501210409
    resourceVersion: "51330"
    uid: 05215cc0-5c04-4957-bb7d-e61527381ff4
  spec:
    sourcePod: network-check-source-869dcfcdcd-r97s6
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:20:00Z"
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 972.407µs
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:48:00Z"
    - latency: 1.708775ms
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:47:00Z"
    - latency: 1.363848ms
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:46:00Z"
    - latency: 14.267487ms
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:45:00Z"
    - latency: 858.522µs
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:44:00Z"
    - latency: 910.173µs
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:43:00Z"
    - latency: 1.05181ms
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:42:00Z"
    - latency: 898.64µs
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:41:00Z"
    - latency: 775.722µs
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:40:00Z"
    - latency: 838.965µs
      message: 'network-check-target-ip-10-0-140-160: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:39:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:12:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-160-to-network-check-target-ip-10-0-143-101
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-160.ec2.internal
      uid: bed5946a-e1ed-4173-bb3e-5b0501210409
    resourceVersion: "51331"
    uid: bff2ce3c-94c6-4717-88c6-fa3165835005
  spec:
    sourcePod: network-check-source-869dcfcdcd-r97s6
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:20:00Z"
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.578847ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:48:00Z"
    - latency: 2.48852ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:47:00Z"
    - latency: 1.883608ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:46:00Z"
    - latency: 7.350516ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:45:00Z"
    - latency: 2.478893ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:44:00Z"
    - latency: 2.287664ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:43:00Z"
    - latency: 2.038819ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:42:00Z"
    - latency: 2.232021ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:41:00Z"
    - latency: 2.022125ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:40:00Z"
    - latency: 1.553782ms
      message: 'network-check-target-ip-10-0-143-101: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:39:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T12:12:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-160-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-160.ec2.internal
      uid: bed5946a-e1ed-4173-bb3e-5b0501210409
    resourceVersion: "52276"
    uid: 2c6b3238-d97b-4d0f-bda4-57a31145b891
  spec:
    sourcePod: network-check-source-869dcfcdcd-r97s6
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T12:19:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.219984ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:49:00Z"
    - latency: 1.900468ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:49:00Z"
    - latency: 1.172442ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:48:00Z"
    - latency: 1.83414ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:48:00Z"
    - latency: 871.872µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:47:00Z"
    - latency: 1.906496ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:47:00Z"
    - latency: 936.016µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:46:00Z"
    - latency: 1.944961ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:46:00Z"
    - latency: 5.8516ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T12:45:00Z"
    - latency: 8.239289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T12:45:00Z"
kind: List
metadata:
  resourceVersion: ""