apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:29:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-132-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-132.us-west-1.compute.internal
      uid: 94843e4d-3cfb-4daf-89e3-1acdfed1463b
    resourceVersion: "24023"
    uid: ccea80f5-96ca-482c-a7b6-b6a624c946ab
  spec:
    sourcePod: network-check-source-6f78d59f99-nqpz4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:36:33Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.466811ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:33Z"
    - latency: 1.055157ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:33Z"
    - latency: 836.887µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:33Z"
    - latency: 1.398643ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:33Z"
    - latency: 1.013911ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:33Z"
    - latency: 1.112211ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:38:33Z"
    - latency: 958.613µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:37:33Z"
    - latency: 1.125866ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:36:33Z"
    - latency: 853.947µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:33Z"
    - latency: 1.056459ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:34:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:29:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-132-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-132.us-west-1.compute.internal
      uid: 94843e4d-3cfb-4daf-89e3-1acdfed1463b
    resourceVersion: "22939"
    uid: 093fe46a-33e9-4a78-899a-b01ac1c1a980
  spec:
    sourcePod: network-check-source-6f78d59f99-nqpz4
    targetEndpoint: aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:35:33Z"
      message: 'load-balancer-api-external: tcp connection to aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.530845ms
      message: 'load-balancer-api-external: tcp connection to aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:33Z"
    - latency: 4.327817ms
      message: 'load-balancer-api-external: resolved host name aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:41:33Z"
    - latency: 52.827393ms
      message: 'load-balancer-api-external: tcp connection to aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:33Z"
    - latency: 4.067383ms
      message: 'load-balancer-api-external: resolved host name aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:40:33Z"
    - latency: 53.519991ms
      message: 'load-balancer-api-external: tcp connection to aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:33Z"
    - latency: 6.650684ms
      message: 'load-balancer-api-external: resolved host name aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:39:33Z"
    - latency: 54.032314ms
      message: 'load-balancer-api-external: tcp connection to aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:38:33Z"
    - latency: 5.171752ms
      message: 'load-balancer-api-external: resolved host name aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:38:33Z"
    - latency: 54.978033ms
      message: 'load-balancer-api-external: tcp connection to aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:37:33Z"
    - latency: 5.502962ms
      message: 'load-balancer-api-external: resolved host name aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:37:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:29:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-132-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-132.us-west-1.compute.internal
      uid: 94843e4d-3cfb-4daf-89e3-1acdfed1463b
    resourceVersion: "22940"
    uid: dacc8863-3dd8-42a5-8bfc-1237b4a0b424
  spec:
    sourcePod: network-check-source-6f78d59f99-nqpz4
    targetEndpoint: aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:35:33Z"
      message: 'load-balancer-api-internal: tcp connection to aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.998248ms
      message: 'load-balancer-api-internal: tcp connection to aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:33Z"
    - latency: 6.757093ms
      message: 'load-balancer-api-internal: resolved host name aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:41:33Z"
    - latency: 52.802613ms
      message: 'load-balancer-api-internal: tcp connection to aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:33Z"
    - latency: 6.671981ms
      message: 'load-balancer-api-internal: resolved host name aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:40:33Z"
    - latency: 53.540029ms
      message: 'load-balancer-api-internal: tcp connection to aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:33Z"
    - latency: 8.424486ms
      message: 'load-balancer-api-internal: resolved host name aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:39:33Z"
    - latency: 54.04118ms
      message: 'load-balancer-api-internal: tcp connection to aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:38:33Z"
    - latency: 7.790813ms
      message: 'load-balancer-api-internal: resolved host name aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:38:33Z"
    - latency: 54.932857ms
      message: 'load-balancer-api-internal: tcp connection to aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:37:33Z"
    - latency: 8.184243ms
      message: 'load-balancer-api-internal: resolved host name aea885a39bc564f9c8b788199a12857e-1a8fee703264910a.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:37:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:29:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-132-to-network-check-target-ip-10-0-130-132
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-132.us-west-1.compute.internal
      uid: 94843e4d-3cfb-4daf-89e3-1acdfed1463b
    resourceVersion: "24020"
    uid: 0aef88b6-5605-4a50-a61b-8e7f1102c872
  spec:
    sourcePod: network-check-source-6f78d59f99-nqpz4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:36:33Z"
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.11332ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:33Z"
    - latency: 1.261283ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:33Z"
    - latency: 1.211568ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:33Z"
    - latency: 1.339671ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:33Z"
    - latency: 1.220838ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:33Z"
    - latency: 1.57614ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:38:33Z"
    - latency: 1.175519ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:37:33Z"
    - latency: 1.003353ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:36:33Z"
    - latency: 921.023µs
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:33Z"
    - latency: 1.000228ms
      message: 'network-check-target-ip-10-0-130-132: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:34:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:29:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-132-to-network-check-target-ip-10-0-138-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-132.us-west-1.compute.internal
      uid: 94843e4d-3cfb-4daf-89e3-1acdfed1463b
    resourceVersion: "24022"
    uid: 7df0cf34-ad30-46b9-95b1-7b5439f62071
  spec:
    sourcePod: network-check-source-6f78d59f99-nqpz4
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:36:33Z"
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.378224ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:33Z"
    - latency: 2.374689ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:33Z"
    - latency: 2.241349ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:33Z"
    - latency: 2.325834ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:33Z"
    - latency: 2.309524ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:33Z"
    - latency: 2.108538ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:38:33Z"
    - latency: 2.293449ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:37:33Z"
    - latency: 2.249226ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:36:33Z"
    - latency: 1.892141ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:33Z"
    - latency: 1.997591ms
      message: 'network-check-target-ip-10-0-138-178: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:34:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:29:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-132-to-network-check-target-ip-10-0-139-39
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-132.us-west-1.compute.internal
      uid: 94843e4d-3cfb-4daf-89e3-1acdfed1463b
    resourceVersion: "24021"
    uid: 246c5cad-18a4-45f8-8b31-81f84ccb8122
  spec:
    sourcePod: network-check-source-6f78d59f99-nqpz4
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:36:33Z"
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.305817ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:33Z"
    - latency: 2.245844ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:33Z"
    - latency: 2.018083ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:33Z"
    - latency: 2.316673ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:33Z"
    - latency: 2.293638ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:33Z"
    - latency: 2.503409ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:38:33Z"
    - latency: 2.333543ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:37:33Z"
    - latency: 2.309571ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:36:33Z"
    - latency: 2.172876ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:33Z"
    - latency: 2.12515ms
      message: 'network-check-target-ip-10-0-139-39: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:34:33Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T21:29:33Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-132-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-132.us-west-1.compute.internal
      uid: 94843e4d-3cfb-4daf-89e3-1acdfed1463b
    resourceVersion: "22937"
    uid: ae218a54-5544-4f53-9aeb-98b7da75c27a
  spec:
    sourcePod: network-check-source-6f78d59f99-nqpz4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T21:35:33Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.009992ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:33Z"
    - latency: 2.001575ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:41:33Z"
    - latency: 1.064877ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:33Z"
    - latency: 2.092638ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:40:33Z"
    - latency: 1.054747ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:33Z"
    - latency: 1.814301ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:39:33Z"
    - latency: 806.425µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:38:33Z"
    - latency: 2.057338ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:38:33Z"
    - latency: 1.25404ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:37:33Z"
    - latency: 1.725245ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:37:33Z"
kind: List
metadata:
  resourceVersion: ""