apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:45:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-222-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-222.ec2.internal
      uid: 40093674-f807-4399-8a2d-2a428062648e
    resourceVersion: "68000"
    uid: 263a7fbc-76b5-4ad5-bd8f-2f307464d098
  spec:
    sourcePod: network-check-source-6f8b768455-52kgm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:52:46Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.045336ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:20:46Z"
    - latency: 929.102µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:19:46Z"
    - latency: 1.742099ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:18:46Z"
    - latency: 985.777µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:17:46Z"
    - latency: 1.231696ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:16:46Z"
    - latency: 1.06724ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:15:46Z"
    - latency: 1.012131ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:14:46Z"
    - latency: 801.027µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:13:46Z"
    - latency: 1.186457ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:12:46Z"
    - latency: 1.352163ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:11:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:45:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-222-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-222.ec2.internal
      uid: 40093674-f807-4399-8a2d-2a428062648e
    resourceVersion: "68893"
    uid: 8989ffbe-e290-499a-92ef-2d136833a5a7
  spec:
    sourcePod: network-check-source-6f8b768455-52kgm
    targetEndpoint: aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:51:46Z"
      message: 'load-balancer-api-external: tcp connection to aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.531405ms
      message: 'load-balancer-api-external: tcp connection to aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:21:46Z"
    - latency: 8.256789ms
      message: 'load-balancer-api-external: resolved host name aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:21:46Z"
    - latency: 6.086818ms
      message: 'load-balancer-api-external: tcp connection to aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:20:46Z"
    - latency: 8.985484ms
      message: 'load-balancer-api-external: resolved host name aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:20:46Z"
    - latency: 4.44644ms
      message: 'load-balancer-api-external: tcp connection to aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:19:46Z"
    - latency: 8.50509ms
      message: 'load-balancer-api-external: resolved host name aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:19:46Z"
    - latency: 6.83127ms
      message: 'load-balancer-api-external: tcp connection to aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:18:46Z"
    - latency: 8.596949ms
      message: 'load-balancer-api-external: resolved host name aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:18:46Z"
    - latency: 3.792593ms
      message: 'load-balancer-api-external: tcp connection to aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:17:46Z"
    - latency: 8.798746ms
      message: 'load-balancer-api-external: resolved host name aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:17:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:45:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-222-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-222.ec2.internal
      uid: 40093674-f807-4399-8a2d-2a428062648e
    resourceVersion: "68894"
    uid: 2339ed04-afe1-4bec-aafc-6bc19650da60
  spec:
    sourcePod: network-check-source-6f8b768455-52kgm
    targetEndpoint: aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:51:46Z"
      message: 'load-balancer-api-internal: tcp connection to aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.159418ms
      message: 'load-balancer-api-internal: tcp connection to aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:21:46Z"
    - latency: 8.281192ms
      message: 'load-balancer-api-internal: resolved host name aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:21:46Z"
    - latency: 5.338298ms
      message: 'load-balancer-api-internal: tcp connection to aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:20:46Z"
    - latency: 9.022745ms
      message: 'load-balancer-api-internal: resolved host name aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:20:46Z"
    - latency: 4.408589ms
      message: 'load-balancer-api-internal: tcp connection to aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:19:46Z"
    - latency: 8.513677ms
      message: 'load-balancer-api-internal: resolved host name aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:19:46Z"
    - latency: 6.83901ms
      message: 'load-balancer-api-internal: tcp connection to aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:18:46Z"
    - latency: 8.67404ms
      message: 'load-balancer-api-internal: resolved host name aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:18:46Z"
    - latency: 4.609684ms
      message: 'load-balancer-api-internal: tcp connection to aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:17:46Z"
    - latency: 8.831333ms
      message: 'load-balancer-api-internal: resolved host name aafe39494f45a4f659afc9e65f7b7996-4e7b0f6011578512.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:17:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:45:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-222-to-network-check-target-ip-10-0-129-226
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-222.ec2.internal
      uid: 40093674-f807-4399-8a2d-2a428062648e
    resourceVersion: "67998"
    uid: ff36f191-98e6-4b3b-acee-5f872e7d91a3
  spec:
    sourcePod: network-check-source-6f8b768455-52kgm
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:52:46Z"
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.397991ms
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:20:46Z"
    - latency: 2.11781ms
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:19:46Z"
    - latency: 2.305548ms
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:18:46Z"
    - latency: 2.338925ms
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:17:46Z"
    - latency: 2.55319ms
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:16:46Z"
    - latency: 2.508152ms
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:15:46Z"
    - latency: 2.528439ms
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:14:46Z"
    - latency: 2.108409ms
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:13:46Z"
    - latency: 2.490881ms
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:12:46Z"
    - latency: 2.393579ms
      message: 'network-check-target-ip-10-0-129-226: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:11:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:45:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-222-to-network-check-target-ip-10-0-139-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-222.ec2.internal
      uid: 40093674-f807-4399-8a2d-2a428062648e
    resourceVersion: "67997"
    uid: 2a99a7fb-bc31-4b0b-9275-9cbeafd328b0
  spec:
    sourcePod: network-check-source-6f8b768455-52kgm
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:52:46Z"
      message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.501799ms
      message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:20:46Z"
    - latency: 2.484218ms
      message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:19:46Z"
    - latency: 2.414391ms
      message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:18:46Z"
    - latency: 2.406418ms
      message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:17:46Z"
    - latency: 2.565113ms
      message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:16:46Z"
    - latency: 2.627822ms
      message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:15:46Z"
    - latency: 2.571687ms
      message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:14:46Z"
    - latency: 2.130875ms
      message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:13:46Z"
    - latency: 2.828928ms
      message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:12:46Z"
    - latency: 3.010276ms
      message: 'network-check-target-ip-10-0-139-34: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:11:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:45:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-222-to-network-check-target-ip-10-0-143-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-222.ec2.internal
      uid: 40093674-f807-4399-8a2d-2a428062648e
    resourceVersion: "67999"
    uid: 56957198-8116-4968-9d56-1caea1060243
  spec:
    sourcePod: network-check-source-6f8b768455-52kgm
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:52:46Z"
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.32862ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:20:46Z"
    - latency: 922.051µs
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:19:46Z"
    - latency: 842.229µs
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:18:46Z"
    - latency: 1.131947ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:17:46Z"
    - latency: 944.264µs
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:16:46Z"
    - latency: 1.006374ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:15:46Z"
    - latency: 1.054425ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:14:46Z"
    - latency: 816.017µs
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:13:46Z"
    - latency: 1.00165ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:12:46Z"
    - latency: 1.417947ms
      message: 'network-check-target-ip-10-0-143-222: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:11:46Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T13:45:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-222-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-222.ec2.internal
      uid: 40093674-f807-4399-8a2d-2a428062648e
    resourceVersion: "68892"
    uid: a0718d8b-6313-4eee-94dc-1297f6dd3cf0
  spec:
    sourcePod: network-check-source-6f8b768455-52kgm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T13:51:46Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.170368ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:21:46Z"
    - latency: 1.853279ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:21:46Z"
    - latency: 853.989µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:20:46Z"
    - latency: 1.721858ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:20:46Z"
    - latency: 1.053175ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:19:46Z"
    - latency: 2.24552ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:19:46Z"
    - latency: 1.000032ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:18:46Z"
    - latency: 2.454161ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:18:46Z"
    - latency: 1.190958ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T14:17:46Z"
    - latency: 1.726021ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T14:17:46Z"
kind: List
metadata:
  resourceVersion: ""