apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T12:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-149-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-149.ec2.internal
      uid: 083f6a27-50b9-4d1d-aab5-74596ad48934
    resourceVersion: "69496"
    uid: fbeb7167-372f-44fa-ad0b-d329d2cdbf97
  spec:
    sourcePod: network-check-source-7cbc45fddc-nxhlt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T12:36:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 740.278µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:04:29Z"
    - latency: 707.547µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:03:29Z"
    - latency: 1.170115ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:02:29Z"
    - latency: 903.492µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:01:29Z"
    - latency: 1.046187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:00:29Z"
    - latency: 880.573µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:59:29Z"
    - latency: 1.715842ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:58:29Z"
    - latency: 1.732154ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:57:29Z"
    - latency: 1.224991ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:56:29Z"
    - latency: 1.266207ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:55:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T12:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-149-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-149.ec2.internal
      uid: 083f6a27-50b9-4d1d-aab5-74596ad48934
    resourceVersion: "70488"
    uid: e3e37067-9443-4b7d-9031-82db8c0bef36
  spec:
    sourcePod: network-check-source-7cbc45fddc-nxhlt
    targetEndpoint: afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T12:35:29Z"
      message: 'load-balancer-api-external: tcp connection to afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.229397ms
      message: 'load-balancer-api-external: tcp connection to afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:05:29Z"
    - latency: 9.585388ms
      message: 'load-balancer-api-external: resolved host name afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:05:29Z"
    - latency: 5.213068ms
      message: 'load-balancer-api-external: tcp connection to afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:04:29Z"
    - latency: 8.283298ms
      message: 'load-balancer-api-external: resolved host name afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:04:29Z"
    - latency: 3.876772ms
      message: 'load-balancer-api-external: tcp connection to afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:03:29Z"
    - latency: 7.634896ms
      message: 'load-balancer-api-external: resolved host name afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:03:29Z"
    - latency: 3.722399ms
      message: 'load-balancer-api-external: tcp connection to afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:02:29Z"
    - latency: 6.154955ms
      message: 'load-balancer-api-external: resolved host name afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:02:29Z"
    - latency: 4.560857ms
      message: 'load-balancer-api-external: tcp connection to afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:01:29Z"
    - latency: 9.152399ms
      message: 'load-balancer-api-external: resolved host name afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:01:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T12:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-149-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-149.ec2.internal
      uid: 083f6a27-50b9-4d1d-aab5-74596ad48934
    resourceVersion: "70487"
    uid: 92046141-ab4c-457f-8b65-a8e6b689698e
  spec:
    sourcePod: network-check-source-7cbc45fddc-nxhlt
    targetEndpoint: afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T12:35:29Z"
      message: 'load-balancer-api-internal: tcp connection to afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.246875ms
      message: 'load-balancer-api-internal: tcp connection to afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:05:29Z"
    - latency: 9.648089ms
      message: 'load-balancer-api-internal: resolved host name afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:05:29Z"
    - latency: 5.122333ms
      message: 'load-balancer-api-internal: tcp connection to afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:04:29Z"
    - latency: 8.190743ms
      message: 'load-balancer-api-internal: resolved host name afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:04:29Z"
    - latency: 3.926955ms
      message: 'load-balancer-api-internal: tcp connection to afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:03:29Z"
    - latency: 7.68769ms
      message: 'load-balancer-api-internal: resolved host name afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:03:29Z"
    - latency: 3.71865ms
      message: 'load-balancer-api-internal: tcp connection to afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:02:29Z"
    - latency: 6.202538ms
      message: 'load-balancer-api-internal: resolved host name afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:02:29Z"
    - latency: 4.628782ms
      message: 'load-balancer-api-internal: tcp connection to afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:01:29Z"
    - latency: 9.212971ms
      message: 'load-balancer-api-internal: resolved host name afa367c0f1fec4197b29e6cdc4854e87-245a67bdb435ac51.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:01:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T12:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-149-to-network-check-target-ip-10-0-131-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-149.ec2.internal
      uid: 083f6a27-50b9-4d1d-aab5-74596ad48934
    resourceVersion: "69493"
    uid: e59bc510-a217-407f-89c7-08ddd86cfc5b
  spec:
    sourcePod: network-check-source-7cbc45fddc-nxhlt
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T12:36:29Z"
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.049331ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:04:29Z"
    - latency: 1.486408ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:03:29Z"
    - latency: 869.676µs
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:02:29Z"
    - latency: 1.074085ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:01:29Z"
    - latency: 1.291262ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:00:29Z"
    - latency: 1.075342ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:59:29Z"
    - latency: 972.268µs
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:58:29Z"
    - latency: 938.968µs
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:57:29Z"
    - latency: 1.532412ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:56:29Z"
    - latency: 1.56419ms
      message: 'network-check-target-ip-10-0-131-149: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:55:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T12:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-149-to-network-check-target-ip-10-0-131-60
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-149.ec2.internal
      uid: 083f6a27-50b9-4d1d-aab5-74596ad48934
    resourceVersion: "69494"
    uid: 4bd66f82-9280-45ea-a82d-099f5cd6565b
  spec:
    sourcePod: network-check-source-7cbc45fddc-nxhlt
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T12:36:29Z"
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.205141ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:04:29Z"
    - latency: 2.139368ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:03:29Z"
    - latency: 2.268777ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:02:29Z"
    - latency: 2.423063ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:01:29Z"
    - latency: 2.349352ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:00:29Z"
    - latency: 2.190257ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:59:29Z"
    - latency: 2.181737ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:58:29Z"
    - latency: 2.357506ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:57:29Z"
    - latency: 2.301674ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:56:29Z"
    - latency: 2.512146ms
      message: 'network-check-target-ip-10-0-131-60: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:55:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T12:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-149-to-network-check-target-ip-10-0-136-161
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-149.ec2.internal
      uid: 083f6a27-50b9-4d1d-aab5-74596ad48934
    resourceVersion: "69495"
    uid: 97beb0d4-2ff6-412c-b362-01b39070de85
  spec:
    sourcePod: network-check-source-7cbc45fddc-nxhlt
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T12:36:29Z"
      message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.829354ms
      message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:04:29Z"
    - latency: 1.614346ms
      message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:03:29Z"
    - latency: 1.957012ms
      message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:02:29Z"
    - latency: 2.012887ms
      message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:01:29Z"
    - latency: 2.033878ms
      message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:00:29Z"
    - latency: 2.149859ms
      message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:59:29Z"
    - latency: 2.017673ms
      message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:58:29Z"
    - latency: 2.131904ms
      message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:57:29Z"
    - latency: 1.964675ms
      message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:56:29Z"
    - latency: 2.212442ms
      message: 'network-check-target-ip-10-0-136-161: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T12:55:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T12:29:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-149-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-149.ec2.internal
      uid: 083f6a27-50b9-4d1d-aab5-74596ad48934
    resourceVersion: "70486"
    uid: f122510c-053b-4f55-bc12-d143cd5fb5dd
  spec:
    sourcePod: network-check-source-7cbc45fddc-nxhlt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T12:35:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 877.122µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:05:29Z"
    - latency: 1.770024ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:05:29Z"
    - latency: 971.275µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:04:29Z"
    - latency: 2.138315ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:04:29Z"
    - latency: 1.08605ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:03:29Z"
    - latency: 2.059328ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:03:29Z"
    - latency: 982.7µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:02:29Z"
    - latency: 1.639512ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:02:29Z"
    - latency: 792.303µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T13:01:29Z"
    - latency: 1.72089ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T13:01:29Z"
kind: List
metadata:
  resourceVersion: ""