apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T05:31:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-93-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-93.ec2.internal
      uid: e9aa7828-de0f-4bfa-aa98-3cb54c5428ae
    resourceVersion: "30701"
    uid: 6454179e-3d5b-4882-939f-8fc3bcb8917a
  spec:
    sourcePod: network-check-source-6947749cfc-wm2dg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T05:38:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 766.2µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:45:23Z"
    - latency: 761.489µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:44:23Z"
    - latency: 814.629µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:43:23Z"
    - latency: 867.913µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:42:23Z"
    - latency: 1.032461ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:41:23Z"
    - latency: 837.165µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:40:23Z"
    - latency: 1.033588ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:39:23Z"
    - latency: 1.183892ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:38:23Z"
    - latency: 838.072µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:37:23Z"
    - latency: 1.145057ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:36:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T05:31:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-93-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-93.ec2.internal
      uid: e9aa7828-de0f-4bfa-aa98-3cb54c5428ae
    resourceVersion: "29354"
    uid: 35c36502-bcfb-4b43-a4fc-f12ea3eef3ef
  spec:
    sourcePod: network-check-source-6947749cfc-wm2dg
    targetEndpoint: a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T05:37:23Z"
      message: 'load-balancer-api-external: tcp connection to a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.884319ms
      message: 'load-balancer-api-external: tcp connection to a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:43:23Z"
    - latency: 9.005096ms
      message: 'load-balancer-api-external: resolved host name a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:43:23Z"
    - latency: 5.012657ms
      message: 'load-balancer-api-external: tcp connection to a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:42:23Z"
    - latency: 8.596202ms
      message: 'load-balancer-api-external: resolved host name a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:42:23Z"
    - latency: 5.106079ms
      message: 'load-balancer-api-external: tcp connection to a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:41:23Z"
    - latency: 7.57842ms
      message: 'load-balancer-api-external: resolved host name a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:41:23Z"
    - latency: 5.516775ms
      message: 'load-balancer-api-external: tcp connection to a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:40:23Z"
    - latency: 8.482311ms
      message: 'load-balancer-api-external: resolved host name a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:40:23Z"
    - latency: 5.460163ms
      message: 'load-balancer-api-external: tcp connection to a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:39:23Z"
    - latency: 7.712186ms
      message: 'load-balancer-api-external: resolved host name a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:39:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T05:31:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-93-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-93.ec2.internal
      uid: e9aa7828-de0f-4bfa-aa98-3cb54c5428ae
    resourceVersion: "29353"
    uid: d702ed5b-2be4-4d8b-a08f-47cca214da16
  spec:
    sourcePod: network-check-source-6947749cfc-wm2dg
    targetEndpoint: a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T05:37:23Z"
      message: 'load-balancer-api-internal: tcp connection to a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.874125ms
      message: 'load-balancer-api-internal: tcp connection to a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:43:23Z"
    - latency: 9.025832ms
      message: 'load-balancer-api-internal: resolved host name a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:43:23Z"
    - latency: 4.991579ms
      message: 'load-balancer-api-internal: tcp connection to a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:42:23Z"
    - latency: 8.63353ms
      message: 'load-balancer-api-internal: resolved host name a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:42:23Z"
    - latency: 5.132865ms
      message: 'load-balancer-api-internal: tcp connection to a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:41:23Z"
    - latency: 7.610319ms
      message: 'load-balancer-api-internal: resolved host name a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:41:23Z"
    - latency: 5.538106ms
      message: 'load-balancer-api-internal: tcp connection to a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:40:23Z"
    - latency: 8.504064ms
      message: 'load-balancer-api-internal: resolved host name a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:40:23Z"
    - latency: 5.394268ms
      message: 'load-balancer-api-internal: tcp connection to a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:39:23Z"
    - latency: 7.680644ms
      message: 'load-balancer-api-internal: resolved host name a0260b72491fa4d749cee3442f8095e9-8ff52f2c58f893c3.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:39:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T05:31:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-93-to-network-check-target-ip-10-0-130-198
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-93.ec2.internal
      uid: e9aa7828-de0f-4bfa-aa98-3cb54c5428ae
    resourceVersion: "30699"
    uid: 1d24fca7-9188-4704-a818-7525d84af4a4
  spec:
    sourcePod: network-check-source-6947749cfc-wm2dg
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T05:38:23Z"
      message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.853687ms
      message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:45:23Z"
    - latency: 1.790649ms
      message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:44:23Z"
    - latency: 2.192895ms
      message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:43:23Z"
    - latency: 1.982862ms
      message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:42:23Z"
    - latency: 2.349577ms
      message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:41:23Z"
    - latency: 2.439867ms
      message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:40:23Z"
    - latency: 2.55914ms
      message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:39:23Z"
    - latency: 2.541726ms
      message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:38:23Z"
    - latency: 2.565972ms
      message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:37:23Z"
    - latency: 2.031119ms
      message: 'network-check-target-ip-10-0-130-198: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:36:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T05:31:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-93-to-network-check-target-ip-10-0-138-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-93.ec2.internal
      uid: e9aa7828-de0f-4bfa-aa98-3cb54c5428ae
    resourceVersion: "30698"
    uid: cadbf74c-a7c3-48bd-ad2b-8912a22a5b3a
  spec:
    sourcePod: network-check-source-6947749cfc-wm2dg
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T05:38:23Z"
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.323169ms
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:45:23Z"
    - latency: 775.169µs
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:44:23Z"
    - latency: 850.774µs
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:43:23Z"
    - latency: 769.336µs
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:42:23Z"
    - latency: 1.199094ms
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:41:23Z"
    - latency: 760.568µs
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:40:23Z"
    - latency: 1.035864ms
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:39:23Z"
    - latency: 831.202µs
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:38:23Z"
    - latency: 982.583µs
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:37:23Z"
    - latency: 949.479µs
      message: 'network-check-target-ip-10-0-138-93: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:36:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T05:31:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-93-to-network-check-target-ip-10-0-140-220
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-93.ec2.internal
      uid: e9aa7828-de0f-4bfa-aa98-3cb54c5428ae
    resourceVersion: "30700"
    uid: 82db92a4-578c-4c94-bcd8-ca7fe8a11e92
  spec:
    sourcePod: network-check-source-6947749cfc-wm2dg
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T05:38:23Z"
      message: 'network-check-target-ip-10-0-140-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.148178ms
      message: 'network-check-target-ip-10-0-140-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:45:23Z"
    - latency: 2.003358ms
      message: 'network-check-target-ip-10-0-140-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:44:23Z"
    - latency: 2.222132ms
      message: 'network-check-target-ip-10-0-140-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:43:23Z"
    - latency: 2.266422ms
      message: 'network-check-target-ip-10-0-140-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:42:23Z"
    - latency: 2.400038ms
      message: 'network-check-target-ip-10-0-140-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:41:23Z"
    - latency: 2.203892ms
      message: 'network-check-target-ip-10-0-140-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:40:23Z"
    - latency: 2.534507ms
      message: 'network-check-target-ip-10-0-140-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:39:23Z"
    - latency: 2.711772ms
      message: 'network-check-target-ip-10-0-140-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:38:23Z"
    - latency: 2.477963ms
      message: 'network-check-target-ip-10-0-140-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:37:23Z"
    - latency: 2.477149ms
      message: 'network-check-target-ip-10-0-140-220: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:36:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-13T05:31:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-93-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-93.ec2.internal
      uid: e9aa7828-de0f-4bfa-aa98-3cb54c5428ae
    resourceVersion: "29352"
    uid: 08a9789b-3168-4515-ab2e-cca16fb5dac7
  spec:
    sourcePod: network-check-source-6947749cfc-wm2dg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-13T05:37:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 908.186µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:43:23Z"
    - latency: 2.440931ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:43:23Z"
    - latency: 736.523µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:42:23Z"
    - latency: 1.674925ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:42:23Z"
    - latency: 708.733µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:41:23Z"
    - latency: 1.698597ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:41:23Z"
    - latency: 788.337µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:40:23Z"
    - latency: 1.617679ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:40:23Z"
    - latency: 1.020592ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-13T05:39:23Z"
    - latency: 1.489343ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-13T05:39:23Z"
kind: List
metadata:
  resourceVersion: ""