apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:01:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-232-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-232.ec2.internal
      uid: e02cbb33-f77a-452d-bdf4-69293a025431
    resourceVersion: "22995"
    uid: 2303b7e1-aa4e-4572-b67f-0f4f8ea0a8c7
  spec:
    sourcePod: network-check-source-7cbc45fddc-jqwrl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:08:39Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 959.124µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:22:39Z"
    - latency: 913.139µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:21:39Z"
    - latency: 1.083451ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:20:39Z"
    - latency: 1.159358ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:19:39Z"
    - latency: 1.088412ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:18:39Z"
    - latency: 885.477µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:17:39Z"
    - latency: 1.337746ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:16:39Z"
    - latency: 933.096µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:15:39Z"
    - latency: 1.126589ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:14:39Z"
    - latency: 990.743µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:13:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:01:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-232-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-232.ec2.internal
      uid: e02cbb33-f77a-452d-bdf4-69293a025431
    resourceVersion: "21596"
    uid: ee3aaf64-e70a-44ad-b2f7-32df4b03f461
  spec:
    sourcePod: network-check-source-7cbc45fddc-jqwrl
    targetEndpoint: aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:07:39Z"
      message: 'load-balancer-api-external: tcp connection to aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.64009ms
      message: 'load-balancer-api-external: tcp connection to aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:19:39Z"
    - latency: 12.164336ms
      message: 'load-balancer-api-external: resolved host name aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:19:39Z"
    - latency: 4.894432ms
      message: 'load-balancer-api-external: tcp connection to aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:18:39Z"
    - latency: 8.595947ms
      message: 'load-balancer-api-external: resolved host name aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:18:39Z"
    - latency: 5.117874ms
      message: 'load-balancer-api-external: tcp connection to aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:17:39Z"
    - latency: 7.328786ms
      message: 'load-balancer-api-external: resolved host name aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:17:39Z"
    - latency: 5.08713ms
      message: 'load-balancer-api-external: tcp connection to aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:16:39Z"
    - latency: 9.909206ms
      message: 'load-balancer-api-external: resolved host name aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:16:39Z"
    - latency: 4.883566ms
      message: 'load-balancer-api-external: tcp connection to aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:15:39Z"
    - latency: 6.832815ms
      message: 'load-balancer-api-external: resolved host name aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:15:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:01:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-232-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-232.ec2.internal
      uid: e02cbb33-f77a-452d-bdf4-69293a025431
    resourceVersion: "21595"
    uid: 1fee9808-61a5-4b4b-bdf7-0555b2b93639
  spec:
    sourcePod: network-check-source-7cbc45fddc-jqwrl
    targetEndpoint: aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:07:39Z"
      message: 'load-balancer-api-internal: tcp connection to aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.629977ms
      message: 'load-balancer-api-internal: tcp connection to aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:19:39Z"
    - latency: 12.210297ms
      message: 'load-balancer-api-internal: resolved host name aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:19:39Z"
    - latency: 4.922662ms
      message: 'load-balancer-api-internal: tcp connection to aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:18:39Z"
    - latency: 8.621918ms
      message: 'load-balancer-api-internal: resolved host name aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:18:39Z"
    - latency: 5.113488ms
      message: 'load-balancer-api-internal: tcp connection to aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:17:39Z"
    - latency: 7.43001ms
      message: 'load-balancer-api-internal: resolved host name aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:17:39Z"
    - latency: 5.033585ms
      message: 'load-balancer-api-internal: tcp connection to aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:16:39Z"
    - latency: 9.955328ms
      message: 'load-balancer-api-internal: resolved host name aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:16:39Z"
    - latency: 4.867699ms
      message: 'load-balancer-api-internal: tcp connection to aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:15:39Z"
    - latency: 6.78911ms
      message: 'load-balancer-api-internal: resolved host name aadb996711f704b01b59ccd7695ea379-9bccad680c2b12b4.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:15:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:01:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-232-to-network-check-target-ip-10-0-130-119
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-232.ec2.internal
      uid: e02cbb33-f77a-452d-bdf4-69293a025431
    resourceVersion: "22994"
    uid: 372724dc-14a3-4d06-84a5-c3ae7ceb276e
  spec:
    sourcePod: network-check-source-7cbc45fddc-jqwrl
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:08:39Z"
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.317428ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:22:39Z"
    - latency: 2.247083ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:21:39Z"
    - latency: 1.933983ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:20:39Z"
    - latency: 2.314563ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:19:39Z"
    - latency: 2.394065ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:18:39Z"
    - latency: 2.510323ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:17:39Z"
    - latency: 2.13895ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:16:39Z"
    - latency: 2.209262ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:15:39Z"
    - latency: 2.301069ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:14:39Z"
    - latency: 2.271752ms
      message: 'network-check-target-ip-10-0-130-119: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:13:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:01:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-232-to-network-check-target-ip-10-0-137-232
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-232.ec2.internal
      uid: e02cbb33-f77a-452d-bdf4-69293a025431
    resourceVersion: "22992"
    uid: de6c4a36-8ed5-44a5-a32f-543ff6fafa1f
  spec:
    sourcePod: network-check-source-7cbc45fddc-jqwrl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:08:39Z"
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 881.057µs
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:22:39Z"
    - latency: 938.218µs
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:21:39Z"
    - latency: 905.805µs
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:20:39Z"
    - latency: 1.564883ms
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:19:39Z"
    - latency: 835.549µs
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:18:39Z"
    - latency: 845.139µs
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:17:39Z"
    - latency: 861.988µs
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:16:39Z"
    - latency: 963.331µs
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:15:39Z"
    - latency: 897.721µs
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:14:39Z"
    - latency: 793.553µs
      message: 'network-check-target-ip-10-0-137-232: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:13:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:01:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-232-to-network-check-target-ip-10-0-139-88
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-232.ec2.internal
      uid: e02cbb33-f77a-452d-bdf4-69293a025431
    resourceVersion: "22993"
    uid: bf76ba86-1a74-453e-9eca-32c4de6e5aca
  spec:
    sourcePod: network-check-source-7cbc45fddc-jqwrl
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:08:39Z"
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.111061ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:22:39Z"
    - latency: 1.765143ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:21:39Z"
    - latency: 1.825662ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:20:39Z"
    - latency: 1.746858ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:19:39Z"
    - latency: 1.601195ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:18:39Z"
    - latency: 2.065103ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:17:39Z"
    - latency: 1.687454ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:16:39Z"
    - latency: 1.931267ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:15:39Z"
    - latency: 1.840901ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:14:39Z"
    - latency: 2.004501ms
      message: 'network-check-target-ip-10-0-139-88: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:13:39Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T22:01:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-232-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-232.ec2.internal
      uid: e02cbb33-f77a-452d-bdf4-69293a025431
    resourceVersion: "21594"
    uid: 7da1c313-ea26-4049-80a9-727933a89dcb
  spec:
    sourcePod: network-check-source-7cbc45fddc-jqwrl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T22:07:39Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.066282ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:19:39Z"
    - latency: 1.805344ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:19:39Z"
    - latency: 871.878µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:18:39Z"
    - latency: 1.906476ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:18:39Z"
    - latency: 932.865µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:17:39Z"
    - latency: 2.083722ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:17:39Z"
    - latency: 929.121µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:16:39Z"
    - latency: 1.914442ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:16:39Z"
    - latency: 1.210118ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:15:39Z"
    - latency: 1.813467ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:15:39Z"
kind: List
metadata:
  resourceVersion: ""