apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:35:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-155-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-155.us-east-2.compute.internal
      uid: f554312e-0e07-4f11-be68-aa2488d95c29
    resourceVersion: "158787"
    uid: 12775f6d-aa06-4faf-8872-d5150a33ec06
  spec:
    sourcePod: network-check-source-6f78d59f99-t9ncn
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:42:02Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.340932ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:24:02Z"
    - latency: 1.182503ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:23:02Z"
    - latency: 1.112045ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:22:02Z"
    - latency: 7.074639ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:21:02Z"
    - latency: 22.870841ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:20:02Z"
    - latency: 4.038792ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:19:02Z"
    - latency: 1.020401ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:18:02Z"
    - latency: 1.73933ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:17:02Z"
    - latency: 2.187024ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:16:02Z"
    - latency: 25.305041ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:15:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:35:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-155-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-155.us-east-2.compute.internal
      uid: f554312e-0e07-4f11-be68-aa2488d95c29
    resourceVersion: "155646"
    uid: f52b0eea-f219-4226-9bf7-e69033e85a4f
  spec:
    sourcePod: network-check-source-6f78d59f99-t9ncn
    targetEndpoint: a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:41:02Z"
      message: 'load-balancer-api-external: tcp connection to a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 24.115976ms
      message: 'load-balancer-api-external: tcp connection to a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:23:02Z"
    - latency: 7.622119ms
      message: 'load-balancer-api-external: resolved host name a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:23:02Z"
    - latency: 4.217095ms
      message: 'load-balancer-api-external: tcp connection to a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:22:02Z"
    - latency: 8.450674ms
      message: 'load-balancer-api-external: resolved host name a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:22:02Z"
    - latency: 8.782567ms
      message: 'load-balancer-api-external: tcp connection to a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:21:02Z"
    - latency: 51.838765ms
      message: 'load-balancer-api-external: resolved host name a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:21:02Z"
    - latency: 10.888696ms
      message: 'load-balancer-api-external: tcp connection to a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:20:02Z"
    - latency: 52.322775ms
      message: 'load-balancer-api-external: resolved host name a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:20:02Z"
    - latency: 5.735935ms
      message: 'load-balancer-api-external: tcp connection to a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:19:02Z"
    - latency: 8.715774ms
      message: 'load-balancer-api-external: resolved host name a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:19:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:35:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-155-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-155.us-east-2.compute.internal
      uid: f554312e-0e07-4f11-be68-aa2488d95c29
    resourceVersion: "155638"
    uid: c1a19011-f925-40e6-92b2-502d93ab800d
  spec:
    sourcePod: network-check-source-6f78d59f99-t9ncn
    targetEndpoint: a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:41:02Z"
      message: 'load-balancer-api-internal: tcp connection to a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.248136ms
      message: 'load-balancer-api-internal: tcp connection to a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:23:02Z"
    - latency: 7.68996ms
      message: 'load-balancer-api-internal: resolved host name a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:23:02Z"
    - latency: 4.727664ms
      message: 'load-balancer-api-internal: tcp connection to a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:22:02Z"
    - latency: 8.481317ms
      message: 'load-balancer-api-internal: resolved host name a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:22:02Z"
    - latency: 8.807861ms
      message: 'load-balancer-api-internal: tcp connection to a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:21:02Z"
    - latency: 49.71081ms
      message: 'load-balancer-api-internal: resolved host name a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:21:02Z"
    - latency: 18.777893ms
      message: 'load-balancer-api-internal: tcp connection to a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:20:02Z"
    - latency: 58.075579ms
      message: 'load-balancer-api-internal: resolved host name a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:20:02Z"
    - latency: 5.785852ms
      message: 'load-balancer-api-internal: tcp connection to a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:19:02Z"
    - latency: 8.168869ms
      message: 'load-balancer-api-internal: resolved host name a97b000890fe34dfd935cea991184764-22fd132c3e50da3b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:19:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:35:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-155-to-network-check-target-ip-10-0-131-155
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-155.us-east-2.compute.internal
      uid: f554312e-0e07-4f11-be68-aa2488d95c29
    resourceVersion: "158784"
    uid: b385933d-d5ba-41d1-b1fe-c42e3fccef62
  spec:
    sourcePod: network-check-source-6f78d59f99-t9ncn
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:42:02Z"
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 944.304µs
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:24:02Z"
    - latency: 1.622617ms
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:23:02Z"
    - latency: 1.059344ms
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:22:02Z"
    - latency: 5.988386ms
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:21:02Z"
    - latency: 42.357074ms
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:20:02Z"
    - latency: 874.753µs
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:19:02Z"
    - latency: 989.173µs
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:18:02Z"
    - latency: 2.042564ms
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:17:02Z"
    - latency: 1.652916ms
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:16:02Z"
    - latency: 25.59814ms
      message: 'network-check-target-ip-10-0-131-155: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:15:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:35:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-155-to-network-check-target-ip-10-0-140-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-155.us-east-2.compute.internal
      uid: f554312e-0e07-4f11-be68-aa2488d95c29
    resourceVersion: "158786"
    uid: 3c29b23e-f9e3-4a84-83c8-30dc9d062b2e
  spec:
    sourcePod: network-check-source-6f78d59f99-t9ncn
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:42:02Z"
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.658357ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:24:02Z"
    - latency: 2.322554ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:23:02Z"
    - latency: 2.531553ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:22:02Z"
    - latency: 8.563098ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:21:02Z"
    - latency: 23.146736ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:20:02Z"
    - latency: 3.886057ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:19:02Z"
    - latency: 2.930328ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:18:02Z"
    - latency: 2.853614ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:17:02Z"
    - latency: 2.281503ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:16:02Z"
    - latency: 57.550362ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:15:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:35:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-155-to-network-check-target-ip-10-0-142-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-155.us-east-2.compute.internal
      uid: f554312e-0e07-4f11-be68-aa2488d95c29
    resourceVersion: "158785"
    uid: 89980bfb-90ba-4e0a-8108-eb00c1b9b8cb
  spec:
    sourcePod: network-check-source-6f78d59f99-t9ncn
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:42:02Z"
      message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.288094ms
      message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:24:02Z"
    - latency: 2.971602ms
      message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:23:02Z"
    - latency: 2.592351ms
      message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:22:02Z"
    - latency: 7.276721ms
      message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:21:02Z"
    - latency: 23.679069ms
      message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:20:02Z"
    - latency: 1.816631ms
      message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:19:02Z"
    - latency: 2.801742ms
      message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:18:02Z"
    - latency: 3.822357ms
      message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:17:02Z"
    - latency: 2.777526ms
      message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:16:02Z"
    - latency: 11.70163ms
      message: 'network-check-target-ip-10-0-142-153: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:15:02Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T18:35:01Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-155-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-155.us-east-2.compute.internal
      uid: f554312e-0e07-4f11-be68-aa2488d95c29
    resourceVersion: "155636"
    uid: 3ee898f3-f71f-4ad8-a673-6b4cd5b24357
  spec:
    sourcePod: network-check-source-6f78d59f99-t9ncn
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T18:41:02Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.147262ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:23:02Z"
    - latency: 2.265509ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:23:02Z"
    - latency: 1.050862ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:22:02Z"
    - latency: 2.03629ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:22:02Z"
    - latency: 12.690665ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:21:02Z"
    - latency: 25.050662ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:21:02Z"
    - latency: 2.121615ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:20:02Z"
    - latency: 43.389565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:20:02Z"
    - latency: 1.694341ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T19:19:02Z"
    - latency: 2.820742ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T19:19:02Z"
kind: List
metadata:
  resourceVersion: ""