apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T22:20:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-37-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-37.ec2.internal
      uid: efffa095-4760-471c-b772-1c785cedbddd
    resourceVersion: "69123"
    uid: a6e78b60-46a6-4a25-8112-5787e810ccfd
  spec:
    sourcePod: network-check-source-7cbc45fddc-jx88m
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:27:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 885.434µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:55:44Z"
    - latency: 826.247µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:54:44Z"
    - latency: 968.354µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:53:44Z"
    - latency: 1.376903ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:52:44Z"
    - latency: 1.090697ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:51:44Z"
    - latency: 1.135356ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:50:44Z"
    - latency: 1.116097ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:49:44Z"
    - latency: 1.006497ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:48:44Z"
    - latency: 1.397343ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:47:44Z"
    - latency: 973.642µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:46:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T22:20:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-37-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-37.ec2.internal
      uid: efffa095-4760-471c-b772-1c785cedbddd
    resourceVersion: "69888"
    uid: bbe80fce-10ad-4b8e-ae66-72678f2094df
  spec:
    sourcePod: network-check-source-7cbc45fddc-jx88m
    targetEndpoint: a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:26:44Z"
      message: 'load-balancer-api-external: tcp connection to a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.022049ms
      message: 'load-balancer-api-external: tcp connection to a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:56:44Z"
    - latency: 9.038826ms
      message: 'load-balancer-api-external: resolved host name a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:56:44Z"
    - latency: 4.850929ms
      message: 'load-balancer-api-external: tcp connection to a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:55:44Z"
    - latency: 9.051939ms
      message: 'load-balancer-api-external: resolved host name a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:55:44Z"
    - latency: 5.069505ms
      message: 'load-balancer-api-external: tcp connection to a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:54:44Z"
    - latency: 8.533724ms
      message: 'load-balancer-api-external: resolved host name a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:54:44Z"
    - latency: 4.219521ms
      message: 'load-balancer-api-external: tcp connection to a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:53:44Z"
    - latency: 8.661142ms
      message: 'load-balancer-api-external: resolved host name a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:53:44Z"
    - latency: 5.653107ms
      message: 'load-balancer-api-external: tcp connection to a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:52:44Z"
    - latency: 10.082125ms
      message: 'load-balancer-api-external: resolved host name a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:52:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T22:20:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-37-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-37.ec2.internal
      uid: efffa095-4760-471c-b772-1c785cedbddd
    resourceVersion: "69889"
    uid: d77f04aa-7d13-46ea-a8fc-d8adfafc88fc
  spec:
    sourcePod: network-check-source-7cbc45fddc-jx88m
    targetEndpoint: a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:26:44Z"
      message: 'load-balancer-api-internal: tcp connection to a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.282876ms
      message: 'load-balancer-api-internal: tcp connection to a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:56:44Z"
    - latency: 9.107335ms
      message: 'load-balancer-api-internal: resolved host name a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:56:44Z"
    - latency: 4.86139ms
      message: 'load-balancer-api-internal: tcp connection to a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:55:44Z"
    - latency: 8.997782ms
      message: 'load-balancer-api-internal: resolved host name a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:55:44Z"
    - latency: 5.033194ms
      message: 'load-balancer-api-internal: tcp connection to a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:54:44Z"
    - latency: 8.60091ms
      message: 'load-balancer-api-internal: resolved host name a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:54:44Z"
    - latency: 5.753188ms
      message: 'load-balancer-api-internal: tcp connection to a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:53:44Z"
    - latency: 8.701737ms
      message: 'load-balancer-api-internal: resolved host name a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:53:44Z"
    - latency: 3.802132ms
      message: 'load-balancer-api-internal: tcp connection to a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:52:44Z"
    - latency: 10.149509ms
      message: 'load-balancer-api-internal: resolved host name a627019127b114ed0af02f697a598be6-bfa5ca75b4963a39.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:52:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T22:20:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-37-to-network-check-target-ip-10-0-129-37
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-37.ec2.internal
      uid: efffa095-4760-471c-b772-1c785cedbddd
    resourceVersion: "69120"
    uid: 6a3f5059-0661-4ac3-b951-ca2cb578403c
  spec:
    sourcePod: network-check-source-7cbc45fddc-jx88m
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:27:44Z"
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.241519ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:55:44Z"
    - latency: 912.636µs
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:54:44Z"
    - latency: 1.332125ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:53:44Z"
    - latency: 1.037966ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:52:44Z"
    - latency: 789.106µs
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:51:44Z"
    - latency: 1.106712ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:50:44Z"
    - latency: 882.403µs
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:49:44Z"
    - latency: 963.34µs
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:48:44Z"
    - latency: 855.246µs
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:47:44Z"
    - latency: 1.085172ms
      message: 'network-check-target-ip-10-0-129-37: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:46:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T22:20:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-37-to-network-check-target-ip-10-0-132-49
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-37.ec2.internal
      uid: efffa095-4760-471c-b772-1c785cedbddd
    resourceVersion: "69121"
    uid: 662fe1fb-75de-4a1d-a020-51e6be566db3
  spec:
    sourcePod: network-check-source-7cbc45fddc-jx88m
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:27:44Z"
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.546758ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:55:44Z"
    - latency: 2.452464ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:54:44Z"
    - latency: 2.393323ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:53:44Z"
    - latency: 2.451723ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:52:44Z"
    - latency: 2.519158ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:51:44Z"
    - latency: 2.397798ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:50:44Z"
    - latency: 2.515619ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:49:44Z"
    - latency: 2.590956ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:48:44Z"
    - latency: 3.024969ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:47:44Z"
    - latency: 2.179182ms
      message: 'network-check-target-ip-10-0-132-49: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:46:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T22:20:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-37-to-network-check-target-ip-10-0-139-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-37.ec2.internal
      uid: efffa095-4760-471c-b772-1c785cedbddd
    resourceVersion: "69122"
    uid: 0d3ee171-02f8-45f9-8643-04967cbad7b8
  spec:
    sourcePod: network-check-source-7cbc45fddc-jx88m
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:27:44Z"
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.762388ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:55:44Z"
    - latency: 2.230148ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:54:44Z"
    - latency: 2.109424ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:53:44Z"
    - latency: 2.533223ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:52:44Z"
    - latency: 2.277453ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:51:44Z"
    - latency: 2.513005ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:50:44Z"
    - latency: 2.528576ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:49:44Z"
    - latency: 2.505497ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:48:44Z"
    - latency: 2.55882ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:47:44Z"
    - latency: 2.590313ms
      message: 'network-check-target-ip-10-0-139-21: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:46:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-18T22:20:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-37-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-37.ec2.internal
      uid: efffa095-4760-471c-b772-1c785cedbddd
    resourceVersion: "69887"
    uid: bbfa2629-d8a9-4f32-aa35-a97ee68b4359
  spec:
    sourcePod: network-check-source-7cbc45fddc-jx88m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-18T22:26:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.016797ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:56:44Z"
    - latency: 1.682277ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:56:44Z"
    - latency: 1.121006ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:55:44Z"
    - latency: 2.217186ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:55:44Z"
    - latency: 1.04075ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:54:44Z"
    - latency: 1.758679ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:54:44Z"
    - latency: 1.044458ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:53:44Z"
    - latency: 1.903658ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:53:44Z"
    - latency: 1.333723ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-18T22:52:44Z"
    - latency: 1.910176ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-18T22:52:44Z"
kind: List
metadata:
  resourceVersion: ""