apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:02:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-13-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-13.ec2.internal
      uid: 95fa925d-4570-4902-9825-7413ef71e4b7
    resourceVersion: "40158"
    uid: d9b4da06-0939-40db-86df-7fe46516d7b7
  spec:
    sourcePod: network-check-source-7cbc45fddc-vmrwf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:09: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.233321ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:51:27Z"
    - latency: 1.067682ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:50:27Z"
    - latency: 1.163173ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:49:27Z"
    - latency: 1.020014ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:48:27Z"
    - latency: 1.151479ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:47:27Z"
    - latency: 977.246µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:46:27Z"
    - latency: 1.600795ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:45:27Z"
    - latency: 1.179827ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:44:27Z"
    - latency: 1.250503ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:43:27Z"
    - latency: 1.088341ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:42:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:02:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-13-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-13.ec2.internal
      uid: 95fa925d-4570-4902-9825-7413ef71e4b7
    resourceVersion: "39739"
    uid: ccb73c42-54c1-47e7-8495-9df96df99ca2
  spec:
    sourcePod: network-check-source-7cbc45fddc-vmrwf
    targetEndpoint: ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:08:27Z"
      message: 'load-balancer-api-external: tcp connection to ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.325474ms
      message: 'load-balancer-api-external: tcp connection to ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:50:27Z"
    - latency: 9.519464ms
      message: 'load-balancer-api-external: resolved host name ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:50:27Z"
    - latency: 4.813854ms
      message: 'load-balancer-api-external: tcp connection to ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:49:27Z"
    - latency: 8.39625ms
      message: 'load-balancer-api-external: resolved host name ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:49:27Z"
    - latency: 5.157133ms
      message: 'load-balancer-api-external: tcp connection to ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:48:27Z"
    - latency: 8.972779ms
      message: 'load-balancer-api-external: resolved host name ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:48:27Z"
    - latency: 5.064883ms
      message: 'load-balancer-api-external: tcp connection to ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:47:27Z"
    - latency: 8.0793ms
      message: 'load-balancer-api-external: resolved host name ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:47:27Z"
    - latency: 3.932398ms
      message: 'load-balancer-api-external: tcp connection to ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:46:27Z"
    - latency: 8.938501ms
      message: 'load-balancer-api-external: resolved host name ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:46:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:02:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-13-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-13.ec2.internal
      uid: 95fa925d-4570-4902-9825-7413ef71e4b7
    resourceVersion: "39740"
    uid: 7cf13a1b-9eee-4ca0-9656-c380a7ae5510
  spec:
    sourcePod: network-check-source-7cbc45fddc-vmrwf
    targetEndpoint: ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:08:27Z"
      message: 'load-balancer-api-internal: tcp connection to ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.782551ms
      message: 'load-balancer-api-internal: tcp connection to ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:50:27Z"
    - latency: 9.402759ms
      message: 'load-balancer-api-internal: resolved host name ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:50:27Z"
    - latency: 4.794016ms
      message: 'load-balancer-api-internal: tcp connection to ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:49:27Z"
    - latency: 8.422ms
      message: 'load-balancer-api-internal: resolved host name ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:49:27Z"
    - latency: 5.350106ms
      message: 'load-balancer-api-internal: tcp connection to ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:48:27Z"
    - latency: 9.043855ms
      message: 'load-balancer-api-internal: resolved host name ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:48:27Z"
    - latency: 5.084433ms
      message: 'load-balancer-api-internal: tcp connection to ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:47:27Z"
    - latency: 8.041641ms
      message: 'load-balancer-api-internal: resolved host name ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:47:27Z"
    - latency: 4.805308ms
      message: 'load-balancer-api-internal: tcp connection to ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:46:27Z"
    - latency: 8.878948ms
      message: 'load-balancer-api-internal: resolved host name ae4828545d7b94898a1444570625a7e7-35503da2fa756608.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:46:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:02:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-13-to-network-check-target-ip-10-0-136-9
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-13.ec2.internal
      uid: 95fa925d-4570-4902-9825-7413ef71e4b7
    resourceVersion: "40156"
    uid: ecece895-87da-4566-b91e-ad449b017adc
  spec:
    sourcePod: network-check-source-7cbc45fddc-vmrwf
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:09:27Z"
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.09395ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:51:27Z"
    - latency: 2.314624ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:50:27Z"
    - latency: 2.264272ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:49:27Z"
    - latency: 2.32329ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:48:27Z"
    - latency: 2.248119ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:47:27Z"
    - latency: 2.10758ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:46:27Z"
    - latency: 2.242845ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:45:27Z"
    - latency: 2.330226ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:44:27Z"
    - latency: 2.38102ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:43:27Z"
    - latency: 2.213035ms
      message: 'network-check-target-ip-10-0-136-9: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:42:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:02:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-13-to-network-check-target-ip-10-0-138-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-13.ec2.internal
      uid: 95fa925d-4570-4902-9825-7413ef71e4b7
    resourceVersion: "40157"
    uid: 95db25ed-5989-465a-a7a7-025d54f02178
  spec:
    sourcePod: network-check-source-7cbc45fddc-vmrwf
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:09:27Z"
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.077755ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:51:27Z"
    - latency: 2.161647ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:50:27Z"
    - latency: 2.146451ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:49:27Z"
    - latency: 2.04388ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:48:27Z"
    - latency: 1.992592ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:47:27Z"
    - latency: 2.445485ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:46:27Z"
    - latency: 2.234372ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:45:27Z"
    - latency: 2.041821ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:44:27Z"
    - latency: 2.327493ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:43:27Z"
    - latency: 2.183174ms
      message: 'network-check-target-ip-10-0-138-45: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:42:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:02:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-13-to-network-check-target-ip-10-0-139-13
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-13.ec2.internal
      uid: 95fa925d-4570-4902-9825-7413ef71e4b7
    resourceVersion: "40155"
    uid: 6f55c078-025c-4cb6-90d6-c53234bbf444
  spec:
    sourcePod: network-check-source-7cbc45fddc-vmrwf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:09:27Z"
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 887.301µs
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:51:27Z"
    - latency: 1.154616ms
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:50:27Z"
    - latency: 879.386µs
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:49:27Z"
    - latency: 1.119958ms
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:48:27Z"
    - latency: 897.572µs
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:47:27Z"
    - latency: 923.463µs
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:46:27Z"
    - latency: 991.951µs
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:45:27Z"
    - latency: 1.051672ms
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:44:27Z"
    - latency: 914.822µs
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:43:27Z"
    - latency: 999.742µs
      message: 'network-check-target-ip-10-0-139-13: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:42:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:02:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-13-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-13.ec2.internal
      uid: 95fa925d-4570-4902-9825-7413ef71e4b7
    resourceVersion: "39737"
    uid: 3d8f6943-61c5-4948-b19c-be55bc2eccdb
  spec:
    sourcePod: network-check-source-7cbc45fddc-vmrwf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:08:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 925.427µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:50:27Z"
    - latency: 1.96929ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:50:27Z"
    - latency: 779.202µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:49:27Z"
    - latency: 1.836006ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:49:27Z"
    - latency: 1.03997ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:48:27Z"
    - latency: 2.178988ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:48:27Z"
    - latency: 934.489µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:47:27Z"
    - latency: 1.816068ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:47:27Z"
    - latency: 858.877µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:46:27Z"
    - latency: 1.871968ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:46:27Z"
kind: List
metadata:
  resourceVersion: ""