apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T20:29:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-142-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-142.ec2.internal
      uid: 43b64e52-72fd-4dd6-b95a-13a6339ace16
    resourceVersion: "53604"
    uid: 16ac0cd2-e4f6-4ae9-ac8a-724d30d66e56
  spec:
    sourcePod: network-check-source-685456655f-htbdg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T20:36:13Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 912.877µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:57:13Z"
    - latency: 993.385µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:56:13Z"
    - latency: 878.8µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:55:13Z"
    - latency: 1.282748ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:54:13Z"
    - latency: 1.149843ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:53:13Z"
    - latency: 1.598634ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:52:13Z"
    - latency: 934.217µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:51:13Z"
    - latency: 1.014286ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:50:13Z"
    - latency: 1.552799ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:49:13Z"
    - latency: 1.025575ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:48:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T20:29:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-142-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-142.ec2.internal
      uid: 43b64e52-72fd-4dd6-b95a-13a6339ace16
    resourceVersion: "55074"
    uid: 4daf7f92-5e3b-4afc-9bb2-dc90f3380268
  spec:
    sourcePod: network-check-source-685456655f-htbdg
    targetEndpoint: a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T20:35:13Z"
      message: 'load-balancer-api-external: tcp connection to a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.743089ms
      message: 'load-balancer-api-external: tcp connection to a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:59:13Z"
    - latency: 6.697918ms
      message: 'load-balancer-api-external: resolved host name a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:59:13Z"
    - latency: 4.276202ms
      message: 'load-balancer-api-external: tcp connection to a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:58:13Z"
    - latency: 7.397577ms
      message: 'load-balancer-api-external: resolved host name a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:58:13Z"
    - latency: 4.398773ms
      message: 'load-balancer-api-external: tcp connection to a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:57:13Z"
    - latency: 6.677692ms
      message: 'load-balancer-api-external: resolved host name a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:57:13Z"
    - latency: 3.634191ms
      message: 'load-balancer-api-external: tcp connection to a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:56:13Z"
    - latency: 7.708257ms
      message: 'load-balancer-api-external: resolved host name a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:56:13Z"
    - latency: 3.929583ms
      message: 'load-balancer-api-external: tcp connection to a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:55:13Z"
    - latency: 7.451929ms
      message: 'load-balancer-api-external: resolved host name a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:55:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T20:29:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-142-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-142.ec2.internal
      uid: 43b64e52-72fd-4dd6-b95a-13a6339ace16
    resourceVersion: "55073"
    uid: 19b07cf7-6319-4683-9727-332eabac3508
  spec:
    sourcePod: network-check-source-685456655f-htbdg
    targetEndpoint: a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T20:35:13Z"
      message: 'load-balancer-api-internal: tcp connection to a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.810212ms
      message: 'load-balancer-api-internal: tcp connection to a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:59:13Z"
    - latency: 6.618011ms
      message: 'load-balancer-api-internal: resolved host name a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:59:13Z"
    - latency: 3.655468ms
      message: 'load-balancer-api-internal: tcp connection to a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:58:13Z"
    - latency: 7.328966ms
      message: 'load-balancer-api-internal: resolved host name a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:58:13Z"
    - latency: 4.965655ms
      message: 'load-balancer-api-internal: tcp connection to a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:57:13Z"
    - latency: 6.57053ms
      message: 'load-balancer-api-internal: resolved host name a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:57:13Z"
    - latency: 5.287087ms
      message: 'load-balancer-api-internal: tcp connection to a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:56:13Z"
    - latency: 7.816166ms
      message: 'load-balancer-api-internal: resolved host name a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:56:13Z"
    - latency: 3.881675ms
      message: 'load-balancer-api-internal: tcp connection to a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:55:13Z"
    - latency: 7.341697ms
      message: 'load-balancer-api-internal: resolved host name a7cd89381595c44aeae1685669b0a41b-a5e1141a1af54eed.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:55:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T20:29:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-142-to-network-check-target-ip-10-0-129-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-142.ec2.internal
      uid: 43b64e52-72fd-4dd6-b95a-13a6339ace16
    resourceVersion: "53603"
    uid: 8b0cf0a9-fddd-411c-a999-79fe35d06a46
  spec:
    sourcePod: network-check-source-685456655f-htbdg
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T20:36:13Z"
      message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.896704ms
      message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:57:13Z"
    - latency: 2.264577ms
      message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:56:13Z"
    - latency: 1.945343ms
      message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:55:13Z"
    - latency: 3.042578ms
      message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:54:13Z"
    - latency: 2.107291ms
      message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:53:13Z"
    - latency: 2.427239ms
      message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:52:13Z"
    - latency: 2.113105ms
      message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:51:13Z"
    - latency: 2.284936ms
      message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:50:13Z"
    - latency: 2.798048ms
      message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:49:13Z"
    - latency: 2.214154ms
      message: 'network-check-target-ip-10-0-129-118: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:48:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T20:29:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-142-to-network-check-target-ip-10-0-132-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-142.ec2.internal
      uid: 43b64e52-72fd-4dd6-b95a-13a6339ace16
    resourceVersion: "53602"
    uid: e2f6c4bf-c057-4243-8278-6b07e6598bd4
  spec:
    sourcePod: network-check-source-685456655f-htbdg
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T20:36:13Z"
      message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.533407ms
      message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:57:13Z"
    - latency: 2.316557ms
      message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:56:13Z"
    - latency: 2.559977ms
      message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:55:13Z"
    - latency: 2.598843ms
      message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:54:13Z"
    - latency: 2.640294ms
      message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:53:13Z"
    - latency: 2.52013ms
      message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:52:13Z"
    - latency: 2.533019ms
      message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:51:13Z"
    - latency: 2.566335ms
      message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:50:13Z"
    - latency: 2.799676ms
      message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:49:13Z"
    - latency: 2.146511ms
      message: 'network-check-target-ip-10-0-132-228: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:48:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T20:29:11Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-142-to-network-check-target-ip-10-0-136-142
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-142.ec2.internal
      uid: 43b64e52-72fd-4dd6-b95a-13a6339ace16
    resourceVersion: "53601"
    uid: 1fe73bba-bd31-4fe2-b2e9-1320aeda99f1
  spec:
    sourcePod: network-check-source-685456655f-htbdg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T20:36:13Z"
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.423985ms
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:57:13Z"
    - latency: 1.544006ms
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:56:13Z"
    - latency: 987.179µs
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:55:13Z"
    - latency: 1.591133ms
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:54:13Z"
    - latency: 1.719288ms
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:53:13Z"
    - latency: 1.923912ms
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:52:13Z"
    - latency: 1.501573ms
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:51:13Z"
    - latency: 1.008992ms
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:50:13Z"
    - latency: 2.079576ms
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:49:13Z"
    - latency: 1.228132ms
      message: 'network-check-target-ip-10-0-136-142: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:48:13Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T20:29:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-142-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-142.ec2.internal
      uid: 43b64e52-72fd-4dd6-b95a-13a6339ace16
    resourceVersion: "55072"
    uid: 93b3b493-3405-4048-8f40-5a02928fd0a4
  spec:
    sourcePod: network-check-source-685456655f-htbdg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T20:35:13Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.499404ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:59:13Z"
    - latency: 1.932385ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:59:13Z"
    - latency: 1.170331ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:58:13Z"
    - latency: 2.123501ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:58:13Z"
    - latency: 783.944µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:57:13Z"
    - latency: 1.754912ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:57:13Z"
    - latency: 1.190646ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:56:13Z"
    - latency: 2.341006ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:56:13Z"
    - latency: 1.157531ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T20:55:13Z"
    - latency: 1.878522ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T20:55:13Z"
kind: List
metadata:
  resourceVersion: ""