apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T22:54:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-69-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-69.ec2.internal
      uid: 63fd31d4-a193-4092-9076-e20b4815a059
    resourceVersion: "45903"
    uid: 11d1d7e7-8314-4632-94ba-3be0f2effcba
  spec:
    sourcePod: network-check-source-6947749cfc-rqrqt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T23:01:15Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.074604ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:22:15Z"
    - latency: 1.325676ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:21:15Z"
    - latency: 1.286512ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:20:15Z"
    - latency: 1.19556ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:19:15Z"
    - latency: 1.062709ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:18:15Z"
    - latency: 1.153693ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:17:15Z"
    - latency: 987.932µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:16:15Z"
    - latency: 1.310327ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:15:15Z"
    - latency: 1.195774ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:14:15Z"
    - latency: 1.596137ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:13:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T22:54:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-69-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-69.ec2.internal
      uid: 63fd31d4-a193-4092-9076-e20b4815a059
    resourceVersion: "48026"
    uid: 8294697a-dcc8-49e6-81f4-db566a1c6f62
  spec:
    sourcePod: network-check-source-6947749cfc-rqrqt
    targetEndpoint: ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T23:00:15Z"
      message: 'load-balancer-api-external: tcp connection to ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.543009ms
      message: 'load-balancer-api-external: tcp connection to ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:24:15Z"
    - latency: 7.882845ms
      message: 'load-balancer-api-external: resolved host name ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:24:15Z"
    - latency: 4.712053ms
      message: 'load-balancer-api-external: tcp connection to ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:23:15Z"
    - latency: 8.294241ms
      message: 'load-balancer-api-external: resolved host name ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:23:15Z"
    - latency: 5.187371ms
      message: 'load-balancer-api-external: tcp connection to ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:22:15Z"
    - latency: 8.031919ms
      message: 'load-balancer-api-external: resolved host name ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:22:15Z"
    - latency: 5.426312ms
      message: 'load-balancer-api-external: tcp connection to ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:21:15Z"
    - latency: 8.681566ms
      message: 'load-balancer-api-external: resolved host name ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:21:15Z"
    - latency: 3.773501ms
      message: 'load-balancer-api-external: tcp connection to ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:20:15Z"
    - latency: 7.776794ms
      message: 'load-balancer-api-external: resolved host name ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:20:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T22:54:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-69-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-69.ec2.internal
      uid: 63fd31d4-a193-4092-9076-e20b4815a059
    resourceVersion: "48025"
    uid: 86358a5e-5aa2-49f3-a94c-df045460ec4c
  spec:
    sourcePod: network-check-source-6947749cfc-rqrqt
    targetEndpoint: ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T23:00:15Z"
      message: 'load-balancer-api-internal: tcp connection to ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.624625ms
      message: 'load-balancer-api-internal: tcp connection to ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:24:15Z"
    - latency: 7.939341ms
      message: 'load-balancer-api-internal: resolved host name ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:24:15Z"
    - latency: 5.542368ms
      message: 'load-balancer-api-internal: tcp connection to ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:23:15Z"
    - latency: 8.346588ms
      message: 'load-balancer-api-internal: resolved host name ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:23:15Z"
    - latency: 5.184538ms
      message: 'load-balancer-api-internal: tcp connection to ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:22:15Z"
    - latency: 8.059298ms
      message: 'load-balancer-api-internal: resolved host name ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:22:15Z"
    - latency: 3.510639ms
      message: 'load-balancer-api-internal: tcp connection to ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:21:15Z"
    - latency: 8.631851ms
      message: 'load-balancer-api-internal: resolved host name ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:21:15Z"
    - latency: 3.696436ms
      message: 'load-balancer-api-internal: tcp connection to ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:20:15Z"
    - latency: 7.843553ms
      message: 'load-balancer-api-internal: resolved host name ab8334b40cfa848078695cec5b674334-e25fe1bf80c5555a.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:20:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T22:54:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-69-to-network-check-target-ip-10-0-128-136
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-69.ec2.internal
      uid: 63fd31d4-a193-4092-9076-e20b4815a059
    resourceVersion: "45902"
    uid: 4963e8d5-6a36-4413-8854-dece6856237d
  spec:
    sourcePod: network-check-source-6947749cfc-rqrqt
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T23:01:15Z"
      message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.841573ms
      message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:22:15Z"
    - latency: 1.987842ms
      message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:21:15Z"
    - latency: 1.996337ms
      message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:20:15Z"
    - latency: 2.04098ms
      message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:19:15Z"
    - latency: 2.007652ms
      message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:18:15Z"
    - latency: 1.776709ms
      message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:17:15Z"
    - latency: 1.730693ms
      message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:16:15Z"
    - latency: 1.970066ms
      message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:15:15Z"
    - latency: 1.978203ms
      message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:14:15Z"
    - latency: 2.208009ms
      message: 'network-check-target-ip-10-0-128-136: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:13:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T22:54:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-69-to-network-check-target-ip-10-0-129-69
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-69.ec2.internal
      uid: 63fd31d4-a193-4092-9076-e20b4815a059
    resourceVersion: "45900"
    uid: 338eae58-94ed-483a-b8e5-a23c0ea1b73b
  spec:
    sourcePod: network-check-source-6947749cfc-rqrqt
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T23:01:15Z"
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.560724ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:22:15Z"
    - latency: 1.236247ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:21:15Z"
    - latency: 1.276723ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:20:15Z"
    - latency: 1.468753ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:19:15Z"
    - latency: 1.658233ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:18:15Z"
    - latency: 805.07µs
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:17:15Z"
    - latency: 1.703813ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:16:15Z"
    - latency: 1.777361ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:15:15Z"
    - latency: 1.303893ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:14:15Z"
    - latency: 1.140213ms
      message: 'network-check-target-ip-10-0-129-69: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:13:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T22:54:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-69-to-network-check-target-ip-10-0-130-203
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-69.ec2.internal
      uid: 63fd31d4-a193-4092-9076-e20b4815a059
    resourceVersion: "45901"
    uid: bb84c91d-723e-421d-af45-6bbbc49c81b7
  spec:
    sourcePod: network-check-source-6947749cfc-rqrqt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T23:01:15Z"
      message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.243304ms
      message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:22:15Z"
    - latency: 2.265116ms
      message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:21:15Z"
    - latency: 2.289199ms
      message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:20:15Z"
    - latency: 2.386778ms
      message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:19:15Z"
    - latency: 2.182429ms
      message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:18:15Z"
    - latency: 2.271678ms
      message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:17:15Z"
    - latency: 2.327341ms
      message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:16:15Z"
    - latency: 2.251121ms
      message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:15:15Z"
    - latency: 2.0545ms
      message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:14:15Z"
    - latency: 2.075392ms
      message: 'network-check-target-ip-10-0-130-203: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:13:15Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-14T22:54:14Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-69-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-69.ec2.internal
      uid: 63fd31d4-a193-4092-9076-e20b4815a059
    resourceVersion: "48024"
    uid: 4bb9cf65-7ba5-497a-aa00-bf32abde1178
  spec:
    sourcePod: network-check-source-6947749cfc-rqrqt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-14T23:00:15Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 922.93µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:24:15Z"
    - latency: 1.73114ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:24:15Z"
    - latency: 770.209µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:23:15Z"
    - latency: 1.93053ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:23:15Z"
    - latency: 1.014565ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:22:15Z"
    - latency: 1.622645ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:22:15Z"
    - latency: 1.104192ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:21:15Z"
    - latency: 1.87462ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:21:15Z"
    - latency: 891.162µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-14T23:20:15Z"
    - latency: 1.713633ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-14T23:20:15Z"
kind: List
metadata:
  resourceVersion: ""