apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-58-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-58.us-east-2.compute.internal
      uid: 2457b259-f0b7-4e8c-a745-739de512eb12
    resourceVersion: "120944"
    uid: c3e1349e-ff08-417e-a3bc-13065909543a
  spec:
    sourcePod: network-check-source-6f78d59f99-hjr2n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 12.143288ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:14:46Z"
    - latency: 1.105969ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:13:46Z"
    - latency: 7.335496ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:12:46Z"
    - latency: 65.732779ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:11:46Z"
    - latency: 1.940823ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:10:46Z"
    - latency: 1.126094ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:09:46Z"
    - latency: 2.815616ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:08:46Z"
    - latency: 1.187696ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:07:46Z"
    - latency: 6.730082ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:06:46Z"
    - latency: 6.284421ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:05:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-58-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-58.us-east-2.compute.internal
      uid: 2457b259-f0b7-4e8c-a745-739de512eb12
    resourceVersion: "125756"
    uid: 02506150-ae20-43a5-a4d7-33871873fe97
  spec:
    sourcePod: network-check-source-6f78d59f99-hjr2n
    targetEndpoint: a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:46Z"
      message: 'load-balancer-api-external: tcp connection to a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.184427ms
      message: 'load-balancer-api-external: tcp connection to a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:15:46Z"
    - latency: 94.615693ms
      message: 'load-balancer-api-external: resolved host name a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:15:46Z"
    - latency: 6.034798ms
      message: 'load-balancer-api-external: tcp connection to a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:14:46Z"
    - latency: 29.482957ms
      message: 'load-balancer-api-external: resolved host name a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:14:46Z"
    - latency: 6.583221ms
      message: 'load-balancer-api-external: tcp connection to a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:13:46Z"
    - latency: 25.582686ms
      message: 'load-balancer-api-external: resolved host name a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:13:46Z"
    - latency: 7.40848ms
      message: 'load-balancer-api-external: tcp connection to a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:12:46Z"
    - latency: 44.221705ms
      message: 'load-balancer-api-external: resolved host name a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:12:46Z"
    - latency: 15.961805ms
      message: 'load-balancer-api-external: tcp connection to a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:11:46Z"
    - latency: 125.574186ms
      message: 'load-balancer-api-external: resolved host name a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:11:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-58-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-58.us-east-2.compute.internal
      uid: 2457b259-f0b7-4e8c-a745-739de512eb12
    resourceVersion: "125755"
    uid: 83837e8d-9728-41ae-9dfe-de285aef0183
  spec:
    sourcePod: network-check-source-6f78d59f99-hjr2n
    targetEndpoint: a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:46Z"
      message: 'load-balancer-api-internal: tcp connection to a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.30163ms
      message: 'load-balancer-api-internal: tcp connection to a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:15:46Z"
    - latency: 87.460876ms
      message: 'load-balancer-api-internal: resolved host name a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:15:46Z"
    - latency: 5.87073ms
      message: 'load-balancer-api-internal: tcp connection to a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:14:46Z"
    - latency: 25.119726ms
      message: 'load-balancer-api-internal: resolved host name a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:14:46Z"
    - latency: 6.738444ms
      message: 'load-balancer-api-internal: tcp connection to a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:13:46Z"
    - latency: 25.260356ms
      message: 'load-balancer-api-internal: resolved host name a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:13:46Z"
    - latency: 7.309804ms
      message: 'load-balancer-api-internal: tcp connection to a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:12:46Z"
    - latency: 45.405718ms
      message: 'load-balancer-api-internal: resolved host name a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:12:46Z"
    - latency: 15.30851ms
      message: 'load-balancer-api-internal: tcp connection to a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:11:46Z"
    - latency: 125.960189ms
      message: 'load-balancer-api-internal: resolved host name a6220e3ad192341079fb5ca2884693b0-319377fd80463d3e.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:11:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-58-to-network-check-target-ip-10-0-133-96
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-58.us-east-2.compute.internal
      uid: 2457b259-f0b7-4e8c-a745-739de512eb12
    resourceVersion: "120941"
    uid: 095c375a-d836-44b6-bcd4-f97cc1fcdfb1
  spec:
    sourcePod: network-check-source-6f78d59f99-hjr2n
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:46Z"
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.246066ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:14:46Z"
    - latency: 2.53752ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:13:46Z"
    - latency: 7.511538ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:12:46Z"
    - latency: 36.568787ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:11:46Z"
    - latency: 4.100468ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:10:46Z"
    - latency: 3.205391ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:09:46Z"
    - latency: 3.53768ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:08:46Z"
    - latency: 2.4596ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:07:46Z"
    - latency: 7.587421ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:06:46Z"
    - latency: 26.500344ms
      message: 'network-check-target-ip-10-0-133-96: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:05:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-58-to-network-check-target-ip-10-0-134-58
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-58.us-east-2.compute.internal
      uid: 2457b259-f0b7-4e8c-a745-739de512eb12
    resourceVersion: "120939"
    uid: d88a3194-5dc8-43fc-8908-8051adbd3ae4
  spec:
    sourcePod: network-check-source-6f78d59f99-hjr2n
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:46Z"
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 7.594945ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:14:46Z"
    - latency: 1.091581ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:13:46Z"
    - latency: 27.381722ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:12:46Z"
    - latency: 37.310027ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:11:46Z"
    - latency: 3.022431ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:10:46Z"
    - latency: 1.119961ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:09:46Z"
    - latency: 3.016794ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:08:46Z"
    - latency: 1.009143ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:07:46Z"
    - latency: 7.142014ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:06:46Z"
    - latency: 5.639801ms
      message: 'network-check-target-ip-10-0-134-58: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:05:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-58-to-network-check-target-ip-10-0-137-135
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-58.us-east-2.compute.internal
      uid: 2457b259-f0b7-4e8c-a745-739de512eb12
    resourceVersion: "120940"
    uid: f489058e-c5df-4e65-be3e-c95422926443
  spec:
    sourcePod: network-check-source-6f78d59f99-hjr2n
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:46:46Z"
      message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.366352ms
      message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:14:46Z"
    - latency: 2.970031ms
      message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:13:46Z"
    - latency: 8.292912ms
      message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:12:46Z"
    - latency: 67.312588ms
      message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:11:46Z"
    - latency: 3.461053ms
      message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:10:46Z"
    - latency: 2.878055ms
      message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:09:46Z"
    - latency: 4.880255ms
      message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:08:46Z"
    - latency: 2.497168ms
      message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:07:46Z"
    - latency: 44.336506ms
      message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:06:46Z"
    - latency: 29.400409ms
      message: 'network-check-target-ip-10-0-137-135: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:05:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:39:45Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-58-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-58.us-east-2.compute.internal
      uid: 2457b259-f0b7-4e8c-a745-739de512eb12
    resourceVersion: "125753"
    uid: 8fd32a6c-0f43-488c-ba3c-50dfd367b1e2
  spec:
    sourcePod: network-check-source-6f78d59f99-hjr2n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:45:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 11.089775ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:15:46Z"
    - latency: 45.345866ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:15:46Z"
    - latency: 1.172649ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:14:46Z"
    - latency: 20.883675ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:14:46Z"
    - latency: 1.186649ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:13:46Z"
    - latency: 2.684018ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:13:46Z"
    - latency: 2.536191ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:12:46Z"
    - latency: 32.509585ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:12:46Z"
    - latency: 7.254358ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:11:46Z"
    - latency: 65.811858ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:11:46Z"
kind: List
metadata:
  resourceVersion: ""