apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:08:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-12-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-12.ec2.internal
      uid: d48537bc-14b0-466b-8d6c-4c2b8abd5303
    resourceVersion: "55085"
    uid: 0a50b043-a35c-4db2-974e-c9e1fa08cda7
  spec:
    sourcePod: network-check-source-989f8b8dc-wtb8n
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:15:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.37397ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:27Z"
    - latency: 896.426µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:27Z"
    - latency: 1.146749ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:27Z"
    - latency: 1.179061ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:27Z"
    - latency: 816.784µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:39:27Z"
    - latency: 859.471µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:38:27Z"
    - latency: 843.826µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:37:27Z"
    - latency: 822.098µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:36:27Z"
    - latency: 935.253µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:35:27Z"
    - latency: 766.354µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:08:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-12-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-12.ec2.internal
      uid: d48537bc-14b0-466b-8d6c-4c2b8abd5303
    resourceVersion: "56066"
    uid: 0f159ec9-b8e7-4b76-ab59-26b75611b06d
  spec:
    sourcePod: network-check-source-989f8b8dc-wtb8n
    targetEndpoint: a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:14:27Z"
      message: 'load-balancer-api-external: tcp connection to a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.267483ms
      message: 'load-balancer-api-external: tcp connection to a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:27Z"
    - latency: 6.839344ms
      message: 'load-balancer-api-external: resolved host name a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:44:27Z"
    - latency: 5.910989ms
      message: 'load-balancer-api-external: tcp connection to a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:27Z"
    - latency: 7.354413ms
      message: 'load-balancer-api-external: resolved host name a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:43:27Z"
    - latency: 5.719203ms
      message: 'load-balancer-api-external: tcp connection to a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:27Z"
    - latency: 6.706029ms
      message: 'load-balancer-api-external: resolved host name a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:42:27Z"
    - latency: 6.971153ms
      message: 'load-balancer-api-external: tcp connection to a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:27Z"
    - latency: 7.003554ms
      message: 'load-balancer-api-external: resolved host name a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:41:27Z"
    - latency: 5.37556ms
      message: 'load-balancer-api-external: tcp connection to a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:27Z"
    - latency: 7.043246ms
      message: 'load-balancer-api-external: resolved host name a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:40:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:08:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-12-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-12.ec2.internal
      uid: d48537bc-14b0-466b-8d6c-4c2b8abd5303
    resourceVersion: "56067"
    uid: 2548b756-66da-405d-8dba-d955c8831968
  spec:
    sourcePod: network-check-source-989f8b8dc-wtb8n
    targetEndpoint: a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:14:27Z"
      message: 'load-balancer-api-internal: tcp connection to a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.315914ms
      message: 'load-balancer-api-internal: tcp connection to a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:27Z"
    - latency: 6.939229ms
      message: 'load-balancer-api-internal: resolved host name a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:44:27Z"
    - latency: 5.431749ms
      message: 'load-balancer-api-internal: tcp connection to a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:27Z"
    - latency: 7.388211ms
      message: 'load-balancer-api-internal: resolved host name a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:43:27Z"
    - latency: 5.704857ms
      message: 'load-balancer-api-internal: tcp connection to a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:27Z"
    - latency: 6.749642ms
      message: 'load-balancer-api-internal: resolved host name a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:42:27Z"
    - latency: 6.923964ms
      message: 'load-balancer-api-internal: tcp connection to a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:27Z"
    - latency: 6.913787ms
      message: 'load-balancer-api-internal: resolved host name a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:41:27Z"
    - latency: 4.687046ms
      message: 'load-balancer-api-internal: tcp connection to a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:27Z"
    - latency: 7.090944ms
      message: 'load-balancer-api-internal: resolved host name a5944888b35044be5bb3bcf343f72f12-3596cf831eb1029e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:40:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:08:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-12-to-network-check-target-ip-10-0-129-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-12.ec2.internal
      uid: d48537bc-14b0-466b-8d6c-4c2b8abd5303
    resourceVersion: "55082"
    uid: 10dc6ef1-27b2-41a0-88ab-525f1dbcc107
  spec:
    sourcePod: network-check-source-989f8b8dc-wtb8n
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:15:27Z"
      message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.175666ms
      message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:27Z"
    - latency: 1.800061ms
      message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:27Z"
    - latency: 2.373803ms
      message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:27Z"
    - latency: 2.35022ms
      message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:27Z"
    - latency: 1.626127ms
      message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:39:27Z"
    - latency: 1.736299ms
      message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:38:27Z"
    - latency: 1.907445ms
      message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:37:27Z"
    - latency: 2.360306ms
      message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:36:27Z"
    - latency: 1.675468ms
      message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:35:27Z"
    - latency: 2.487313ms
      message: 'network-check-target-ip-10-0-129-80: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:08:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-12-to-network-check-target-ip-10-0-134-25
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-12.ec2.internal
      uid: d48537bc-14b0-466b-8d6c-4c2b8abd5303
    resourceVersion: "55084"
    uid: 124ec2b0-87cf-455f-aa51-b1c2d10d5f36
  spec:
    sourcePod: network-check-source-989f8b8dc-wtb8n
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:15:27Z"
      message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.625307ms
      message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:27Z"
    - latency: 1.342907ms
      message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:27Z"
    - latency: 2.248643ms
      message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:27Z"
    - latency: 1.899491ms
      message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:27Z"
    - latency: 1.517497ms
      message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:39:27Z"
    - latency: 1.601855ms
      message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:38:27Z"
    - latency: 1.909206ms
      message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:37:27Z"
    - latency: 1.833341ms
      message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:36:27Z"
    - latency: 1.505281ms
      message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:35:27Z"
    - latency: 1.732014ms
      message: 'network-check-target-ip-10-0-134-25: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:08:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-12-to-network-check-target-ip-10-0-142-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-12.ec2.internal
      uid: d48537bc-14b0-466b-8d6c-4c2b8abd5303
    resourceVersion: "55083"
    uid: 483a1fd0-544d-46a0-88c7-f6ff1419e4c4
  spec:
    sourcePod: network-check-source-989f8b8dc-wtb8n
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:15:27Z"
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.082941ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:27Z"
    - latency: 870.038µs
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:27Z"
    - latency: 1.326609ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:27Z"
    - latency: 1.398344ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:27Z"
    - latency: 869.899µs
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:39:27Z"
    - latency: 1.603456ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:38:27Z"
    - latency: 1.596754ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:37:27Z"
    - latency: 910.245µs
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:36:27Z"
    - latency: 828.334µs
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:35:27Z"
    - latency: 1.056314ms
      message: 'network-check-target-ip-10-0-142-12: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:08:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-12-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-12.ec2.internal
      uid: d48537bc-14b0-466b-8d6c-4c2b8abd5303
    resourceVersion: "56065"
    uid: dcb83f10-bda9-44eb-8bb3-0e48f9b82b03
  spec:
    sourcePod: network-check-source-989f8b8dc-wtb8n
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:14:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 874.81µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:27Z"
    - latency: 1.792635ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:44:27Z"
    - latency: 906.183µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:27Z"
    - latency: 1.937942ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:43:27Z"
    - latency: 1.088839ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:27Z"
    - latency: 1.706001ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:42:27Z"
    - latency: 1.000611ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:27Z"
    - latency: 2.17518ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:41:27Z"
    - latency: 1.333287ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:27Z"
    - latency: 2.006247ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:40:27Z"
kind: List
metadata:
  resourceVersion: ""