apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:52:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: 6854102b-31d8-4b92-a711-63edcce5a3c4
    resourceVersion: "53838"
    uid: db867100-1dc0-497c-aac5-0792f8b832ab
  spec:
    sourcePod: network-check-source-6f8b768455-jfnfq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:00:00Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 961.931µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:21:00Z"
    - latency: 1.483314ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:20:00Z"
    - latency: 1.290489ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:19:00Z"
    - latency: 1.292491ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:18:00Z"
    - latency: 1.072002ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:17:00Z"
    - latency: 1.34199ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:16:00Z"
    - latency: 927.988µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:15:00Z"
    - latency: 1.020097ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:14:00Z"
    - latency: 1.102201ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:13:00Z"
    - latency: 1.108984ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:12:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:52:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: 6854102b-31d8-4b92-a711-63edcce5a3c4
    resourceVersion: "55817"
    uid: cba943d7-a80c-4681-ac43-3ed7bcaa07c3
  spec:
    sourcePod: network-check-source-6f8b768455-jfnfq
    targetEndpoint: a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T03:59:00Z"
      message: 'load-balancer-api-external: tcp connection to a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.878398ms
      message: 'load-balancer-api-external: tcp connection to a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:23:00Z"
    - latency: 7.349275ms
      message: 'load-balancer-api-external: resolved host name a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:23:00Z"
    - latency: 3.317516ms
      message: 'load-balancer-api-external: tcp connection to a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:22:00Z"
    - latency: 8.207133ms
      message: 'load-balancer-api-external: resolved host name a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:22:00Z"
    - latency: 4.21221ms
      message: 'load-balancer-api-external: tcp connection to a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:21:00Z"
    - latency: 9.393053ms
      message: 'load-balancer-api-external: resolved host name a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:21:00Z"
    - latency: 3.302628ms
      message: 'load-balancer-api-external: tcp connection to a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:20:00Z"
    - latency: 8.996178ms
      message: 'load-balancer-api-external: resolved host name a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:20:00Z"
    - latency: 5.37868ms
      message: 'load-balancer-api-external: tcp connection to a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:19:00Z"
    - latency: 11.794374ms
      message: 'load-balancer-api-external: resolved host name a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:19:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:52:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: 6854102b-31d8-4b92-a711-63edcce5a3c4
    resourceVersion: "55818"
    uid: 203173b5-b2bf-4078-a358-2711662114e7
  spec:
    sourcePod: network-check-source-6f8b768455-jfnfq
    targetEndpoint: a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T03:59:00Z"
      message: 'load-balancer-api-internal: tcp connection to a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.492691ms
      message: 'load-balancer-api-internal: tcp connection to a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:23:00Z"
    - latency: 7.313262ms
      message: 'load-balancer-api-internal: resolved host name a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:23:00Z"
    - latency: 3.877551ms
      message: 'load-balancer-api-internal: tcp connection to a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:22:00Z"
    - latency: 8.253136ms
      message: 'load-balancer-api-internal: resolved host name a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:22:00Z"
    - latency: 4.336949ms
      message: 'load-balancer-api-internal: tcp connection to a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:21:00Z"
    - latency: 9.38197ms
      message: 'load-balancer-api-internal: resolved host name a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:21:00Z"
    - latency: 3.522249ms
      message: 'load-balancer-api-internal: tcp connection to a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:20:00Z"
    - latency: 9.131053ms
      message: 'load-balancer-api-internal: resolved host name a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:20:00Z"
    - latency: 5.210281ms
      message: 'load-balancer-api-internal: tcp connection to a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:19:00Z"
    - latency: 11.762585ms
      message: 'load-balancer-api-internal: resolved host name a04244b585a7a4ae99ed3d284aa3ff01-38b372238a4808df.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:19:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:52:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-network-check-target-ip-10-0-131-122
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: 6854102b-31d8-4b92-a711-63edcce5a3c4
    resourceVersion: "53837"
    uid: 1c2354fe-2fac-48fc-9058-7cf3c5857283
  spec:
    sourcePod: network-check-source-6f8b768455-jfnfq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:00:00Z"
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.96689ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:21:00Z"
    - latency: 2.268779ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:20:00Z"
    - latency: 2.164595ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:19:00Z"
    - latency: 2.17489ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:18:00Z"
    - latency: 2.254344ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:17:00Z"
    - latency: 2.38389ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:16:00Z"
    - latency: 2.221879ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:15:00Z"
    - latency: 1.958413ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:14:00Z"
    - latency: 2.047436ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:13:00Z"
    - latency: 1.776006ms
      message: 'network-check-target-ip-10-0-131-122: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:12:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:52:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-network-check-target-ip-10-0-140-70
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: 6854102b-31d8-4b92-a711-63edcce5a3c4
    resourceVersion: "53835"
    uid: 214eb777-5fa5-4ef6-803c-fd676ba0223f
  spec:
    sourcePod: network-check-source-6f8b768455-jfnfq
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:00:00Z"
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 903.152µs
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:21:00Z"
    - latency: 917.749µs
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:20:00Z"
    - latency: 1.872542ms
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:19:00Z"
    - latency: 1.395333ms
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:18:00Z"
    - latency: 1.194999ms
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:17:00Z"
    - latency: 1.595476ms
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:16:00Z"
    - latency: 1.183981ms
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:15:00Z"
    - latency: 841.628µs
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:14:00Z"
    - latency: 1.001019ms
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:13:00Z"
    - latency: 841.098µs
      message: 'network-check-target-ip-10-0-140-70: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:12:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:52:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-network-check-target-ip-10-0-142-242
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: 6854102b-31d8-4b92-a711-63edcce5a3c4
    resourceVersion: "53836"
    uid: 4702403f-bb84-472e-92b6-4f79ae3b5283
  spec:
    sourcePod: network-check-source-6f8b768455-jfnfq
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T04:00:00Z"
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.93289ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:21:00Z"
    - latency: 2.159167ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:20:00Z"
    - latency: 2.137557ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:19:00Z"
    - latency: 2.058873ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:18:00Z"
    - latency: 2.31554ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:17:00Z"
    - latency: 2.337944ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:16:00Z"
    - latency: 2.202533ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:15:00Z"
    - latency: 2.373958ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:14:00Z"
    - latency: 2.246471ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:13:00Z"
    - latency: 2.330843ms
      message: 'network-check-target-ip-10-0-142-242: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:12:00Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-11T03:52:59Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-70-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-70.ec2.internal
      uid: 6854102b-31d8-4b92-a711-63edcce5a3c4
    resourceVersion: "55816"
    uid: 6cb80978-8a7b-43b6-9d75-e8f39caf2123
  spec:
    sourcePod: network-check-source-6f8b768455-jfnfq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-11T03:59:00Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 993.452µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:23:00Z"
    - latency: 2.110758ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:23:00Z"
    - latency: 1.061223ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:22:00Z"
    - latency: 1.818446ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:22:00Z"
    - latency: 992.066µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:21:00Z"
    - latency: 1.843432ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:21:00Z"
    - latency: 802.803µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:20:00Z"
    - latency: 2.204719ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:20:00Z"
    - latency: 1.116782ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-11T04:19:00Z"
    - latency: 2.076859ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-11T04:19:00Z"
kind: List
metadata:
  resourceVersion: ""