apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T13:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-215-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-215.ec2.internal
      uid: a63f16e4-20d2-408d-80cc-6c1e8476b300
    resourceVersion: "63707"
    uid: 907361f8-f7db-4eed-8c3b-f953c2f4d468
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6d7cc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T13:57:51Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.193846ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:32:51Z"
    - latency: 812.448µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:31:51Z"
    - latency: 1.132219ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:30:51Z"
    - latency: 935.755µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:29:51Z"
    - latency: 879.149µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:28:51Z"
    - latency: 1.203453ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:27:51Z"
    - latency: 952.358µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:26:51Z"
    - latency: 981.852µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:25:51Z"
    - latency: 1.041961ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:24:51Z"
    - latency: 1.437326ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T13:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-215-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-215.ec2.internal
      uid: a63f16e4-20d2-408d-80cc-6c1e8476b300
    resourceVersion: "63709"
    uid: c1985d98-e794-4022-bbf2-feaf9e5218de
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6d7cc
    targetEndpoint: a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T13:56:51Z"
      message: 'load-balancer-api-external: tcp connection to a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.156452ms
      message: 'load-balancer-api-external: tcp connection to a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:32:51Z"
    - latency: 8.19191ms
      message: 'load-balancer-api-external: resolved host name a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:32:51Z"
    - latency: 3.802499ms
      message: 'load-balancer-api-external: tcp connection to a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:31:51Z"
    - latency: 11.02627ms
      message: 'load-balancer-api-external: resolved host name a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:31:51Z"
    - latency: 5.103622ms
      message: 'load-balancer-api-external: tcp connection to a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:30:51Z"
    - latency: 7.994265ms
      message: 'load-balancer-api-external: resolved host name a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:30:51Z"
    - latency: 3.642808ms
      message: 'load-balancer-api-external: tcp connection to a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:29:51Z"
    - latency: 10.942598ms
      message: 'load-balancer-api-external: resolved host name a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:29:51Z"
    - latency: 3.652877ms
      message: 'load-balancer-api-external: tcp connection to a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:28:51Z"
    - latency: 13.367386ms
      message: 'load-balancer-api-external: resolved host name a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:28:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T13:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-215-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-215.ec2.internal
      uid: a63f16e4-20d2-408d-80cc-6c1e8476b300
    resourceVersion: "63708"
    uid: 12353d6f-e354-4a01-a976-1690a5aff89c
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6d7cc
    targetEndpoint: a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T13:56:51Z"
      message: 'load-balancer-api-internal: tcp connection to a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.013925ms
      message: 'load-balancer-api-internal: tcp connection to a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:32:51Z"
    - latency: 8.092917ms
      message: 'load-balancer-api-internal: resolved host name a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:32:51Z"
    - latency: 4.063678ms
      message: 'load-balancer-api-internal: tcp connection to a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:31:51Z"
    - latency: 10.996036ms
      message: 'load-balancer-api-internal: resolved host name a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:31:51Z"
    - latency: 4.658456ms
      message: 'load-balancer-api-internal: tcp connection to a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:30:51Z"
    - latency: 7.928849ms
      message: 'load-balancer-api-internal: resolved host name a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:30:51Z"
    - latency: 3.663943ms
      message: 'load-balancer-api-internal: tcp connection to a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:29:51Z"
    - latency: 10.909661ms
      message: 'load-balancer-api-internal: resolved host name a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:29:51Z"
    - latency: 3.576786ms
      message: 'load-balancer-api-internal: tcp connection to a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:28:51Z"
    - latency: 13.296457ms
      message: 'load-balancer-api-internal: resolved host name a80032f8fed33441297f63d5a3b8568d-2e419396d1f789d7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:28:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T13:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-215-to-network-check-target-ip-10-0-129-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-215.ec2.internal
      uid: a63f16e4-20d2-408d-80cc-6c1e8476b300
    resourceVersion: "63704"
    uid: c553f99e-393a-4add-9ae3-f93a3ea1bfec
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6d7cc
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T13:57:51Z"
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.235916ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:32:51Z"
    - latency: 2.158146ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:31:51Z"
    - latency: 2.144899ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:30:51Z"
    - latency: 2.408459ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:29:51Z"
    - latency: 2.164786ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:28:51Z"
    - latency: 2.103544ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:27:51Z"
    - latency: 2.466136ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:26:51Z"
    - latency: 2.173316ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:25:51Z"
    - latency: 1.780318ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:24:51Z"
    - latency: 2.465557ms
      message: 'network-check-target-ip-10-0-129-134: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T13:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-215-to-network-check-target-ip-10-0-131-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-215.ec2.internal
      uid: a63f16e4-20d2-408d-80cc-6c1e8476b300
    resourceVersion: "63705"
    uid: 54181e1a-7ae2-4d44-9337-3f04fe3a36a9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6d7cc
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T13:57:51Z"
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.938145ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:32:51Z"
    - latency: 1.802038ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:31:51Z"
    - latency: 2.319221ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:30:51Z"
    - latency: 1.817634ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:29:51Z"
    - latency: 1.852391ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:28:51Z"
    - latency: 2.143219ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:27:51Z"
    - latency: 2.134299ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:26:51Z"
    - latency: 2.111323ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:25:51Z"
    - latency: 2.215818ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:24:51Z"
    - latency: 1.854148ms
      message: 'network-check-target-ip-10-0-131-79: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T13:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-215-to-network-check-target-ip-10-0-140-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-215.ec2.internal
      uid: a63f16e4-20d2-408d-80cc-6c1e8476b300
    resourceVersion: "63703"
    uid: 6d3c54a4-29ac-41d7-8f94-3e79d56b3293
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6d7cc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T13:57:51Z"
      message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 958.678µs
      message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:32:51Z"
    - latency: 1.008899ms
      message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:31:51Z"
    - latency: 1.10195ms
      message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:30:51Z"
    - latency: 869.094µs
      message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:29:51Z"
    - latency: 866.912µs
      message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:28:51Z"
    - latency: 1.432908ms
      message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:27:51Z"
    - latency: 1.377339ms
      message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:26:51Z"
    - latency: 1.256873ms
      message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:25:51Z"
    - latency: 858.26µs
      message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:24:51Z"
    - latency: 1.021739ms
      message: 'network-check-target-ip-10-0-140-215: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:23:51Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-22T13:50:50Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-215-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-215.ec2.internal
      uid: a63f16e4-20d2-408d-80cc-6c1e8476b300
    resourceVersion: "63706"
    uid: 3d6615c7-58f4-44b2-980a-3e1a85ac6517
  spec:
    sourcePod: network-check-source-7bc5b6bf85-6d7cc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-22T13:56:51Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 929.223µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:32:51Z"
    - latency: 1.751658ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:32:51Z"
    - latency: 909.121µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:31:51Z"
    - latency: 1.826708ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:31:51Z"
    - latency: 1.16008ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:30:51Z"
    - latency: 1.723176ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:30:51Z"
    - latency: 938.124µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:29:51Z"
    - latency: 1.797162ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:29:51Z"
    - latency: 952.274µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-22T14:28:51Z"
    - latency: 1.931885ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-22T14:28:51Z"
kind: List
metadata:
  resourceVersion: ""