apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:38:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 0ce14ee2-80d9-4387-9493-96036b32ef79
    resourceVersion: "68238"
    uid: 427b94a2-5f8c-4961-be60-df29f9546c44
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cc9pp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:45:12Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.13358ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:27:12Z"
    - latency: 1.408404ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:26:12Z"
    - latency: 1.245772ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:25:12Z"
    - latency: 1.178342ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:24:12Z"
    - latency: 1.432645ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:23:12Z"
    - latency: 1.599029ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:22:12Z"
    - latency: 1.149215ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:21:12Z"
    - latency: 1.068492ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:20:12Z"
    - latency: 1.008862ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:19:12Z"
    - latency: 1.086672ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:18:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:38:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 0ce14ee2-80d9-4387-9493-96036b32ef79
    resourceVersion: "67210"
    uid: b1c010ee-f87b-43f9-8b1d-a5520f66e583
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cc9pp
    targetEndpoint: a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:44:12Z"
      message: 'load-balancer-api-external: tcp connection to a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.211793ms
      message: 'load-balancer-api-external: tcp connection to a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:26:12Z"
    - latency: 9.88995ms
      message: 'load-balancer-api-external: resolved host name a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:26:12Z"
    - latency: 4.638378ms
      message: 'load-balancer-api-external: tcp connection to a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:25:12Z"
    - latency: 9.026239ms
      message: 'load-balancer-api-external: resolved host name a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:25:12Z"
    - latency: 4.177115ms
      message: 'load-balancer-api-external: tcp connection to a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:24:12Z"
    - latency: 7.754153ms
      message: 'load-balancer-api-external: resolved host name a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:24:12Z"
    - latency: 3.976245ms
      message: 'load-balancer-api-external: tcp connection to a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:23:12Z"
    - latency: 6.895011ms
      message: 'load-balancer-api-external: resolved host name a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:23:12Z"
    - latency: 4.892599ms
      message: 'load-balancer-api-external: tcp connection to a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:22:12Z"
    - latency: 7.402841ms
      message: 'load-balancer-api-external: resolved host name a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:22:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:38:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 0ce14ee2-80d9-4387-9493-96036b32ef79
    resourceVersion: "67211"
    uid: d4eab53a-632f-4795-8b58-5c252050fce5
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cc9pp
    targetEndpoint: a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:44:12Z"
      message: 'load-balancer-api-internal: tcp connection to a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.776509ms
      message: 'load-balancer-api-internal: tcp connection to a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:26:12Z"
    - latency: 10.011669ms
      message: 'load-balancer-api-internal: resolved host name a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:26:12Z"
    - latency: 5.331072ms
      message: 'load-balancer-api-internal: tcp connection to a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:25:12Z"
    - latency: 9.074045ms
      message: 'load-balancer-api-internal: resolved host name a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:25:12Z"
    - latency: 5.744753ms
      message: 'load-balancer-api-internal: tcp connection to a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:24:12Z"
    - latency: 7.960104ms
      message: 'load-balancer-api-internal: resolved host name a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:24:12Z"
    - latency: 3.985945ms
      message: 'load-balancer-api-internal: tcp connection to a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:23:12Z"
    - latency: 6.863642ms
      message: 'load-balancer-api-internal: resolved host name a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:23:12Z"
    - latency: 4.875708ms
      message: 'load-balancer-api-internal: tcp connection to a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:22:12Z"
    - latency: 7.4841ms
      message: 'load-balancer-api-internal: resolved host name a27ee68f7022e4ef58573be0c2daba62-94a1bd04fd6444cf.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:22:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:38:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-network-check-target-ip-10-0-134-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 0ce14ee2-80d9-4387-9493-96036b32ef79
    resourceVersion: "68236"
    uid: 214e5d59-7bd2-4bec-89e4-c0758446714c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cc9pp
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:45:12Z"
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.327871ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:27:12Z"
    - latency: 2.620411ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:26:12Z"
    - latency: 2.684881ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:25:12Z"
    - latency: 2.232996ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:24:12Z"
    - latency: 2.743222ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:23:12Z"
    - latency: 2.762076ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:22:12Z"
    - latency: 2.518516ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:21:12Z"
    - latency: 2.555915ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:20:12Z"
    - latency: 2.5319ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:19:12Z"
    - latency: 2.332886ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:18:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:38:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-network-check-target-ip-10-0-139-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 0ce14ee2-80d9-4387-9493-96036b32ef79
    resourceVersion: "68235"
    uid: 84a7bc30-c1e4-4164-9519-c6b1bfbcee23
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cc9pp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:45:12Z"
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.005842ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:27:12Z"
    - latency: 1.039945ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:26:12Z"
    - latency: 1.040505ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:25:12Z"
    - latency: 933.965µs
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:24:12Z"
    - latency: 1.19751ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:23:12Z"
    - latency: 1.548508ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:22:12Z"
    - latency: 1.348841ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:21:12Z"
    - latency: 1.386594ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:20:12Z"
    - latency: 1.080405ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:19:12Z"
    - latency: 1.075185ms
      message: 'network-check-target-ip-10-0-139-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:18:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:38:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-network-check-target-ip-10-0-140-146
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 0ce14ee2-80d9-4387-9493-96036b32ef79
    resourceVersion: "68237"
    uid: af044d86-ccb9-45ad-9007-0fde6988afd9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cc9pp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:45:12Z"
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.733624ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:27:12Z"
    - latency: 2.644092ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:26:12Z"
    - latency: 2.61761ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:25:12Z"
    - latency: 2.555507ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:24:12Z"
    - latency: 2.399399ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:23:12Z"
    - latency: 2.568117ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:22:12Z"
    - latency: 2.157166ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:21:12Z"
    - latency: 2.407667ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:20:12Z"
    - latency: 2.322538ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:19:12Z"
    - latency: 2.674166ms
      message: 'network-check-target-ip-10-0-140-146: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:18:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-16T22:38:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-23-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-23.ec2.internal
      uid: 0ce14ee2-80d9-4387-9493-96036b32ef79
    resourceVersion: "67208"
    uid: c1bf3393-e499-4b51-b3d3-5c3fd34e8711
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cc9pp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-16T22:44:12Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.020136ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:26:12Z"
    - latency: 2.023409ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:26:12Z"
    - latency: 794.993µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:25:12Z"
    - latency: 1.898578ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:25:12Z"
    - latency: 995.66µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:24:12Z"
    - latency: 1.884351ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:24:12Z"
    - latency: 1.408265ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:23:12Z"
    - latency: 1.917403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:23:12Z"
    - latency: 1.030881ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-16T23:22:12Z"
    - latency: 1.813261ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-16T23:22:12Z"
kind: List
metadata:
  resourceVersion: ""