apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T09:46:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-247-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-247.ec2.internal
      uid: 3e224d11-06f7-43fa-9f97-8c2ca46726c8
    resourceVersion: "67228"
    uid: bf5f505d-5617-4a5f-9ab5-66a6a16c8dcf
  spec:
    sourcePod: network-check-source-6f8b768455-lzhmx
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T09:53:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.211539ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:21:47Z"
    - latency: 1.175004ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:20:47Z"
    - latency: 1.200878ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:19:47Z"
    - latency: 1.319623ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:18:47Z"
    - latency: 966.818µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:17:47Z"
    - latency: 1.212576ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:16:47Z"
    - latency: 1.191615ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:15:47Z"
    - latency: 1.08126ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:14:47Z"
    - latency: 1.142808ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:13:47Z"
    - latency: 1.203161ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:12:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T09:46:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-247-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-247.ec2.internal
      uid: 3e224d11-06f7-43fa-9f97-8c2ca46726c8
    resourceVersion: "68302"
    uid: 9932908f-b766-4321-b0c8-2b37628eeb11
  spec:
    sourcePod: network-check-source-6f8b768455-lzhmx
    targetEndpoint: afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T09:52:47Z"
      message: 'load-balancer-api-external: tcp connection to afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.444242ms
      message: 'load-balancer-api-external: tcp connection to afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:22:47Z"
    - latency: 7.792145ms
      message: 'load-balancer-api-external: resolved host name afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:22:47Z"
    - latency: 3.991866ms
      message: 'load-balancer-api-external: tcp connection to afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:21:47Z"
    - latency: 7.113449ms
      message: 'load-balancer-api-external: resolved host name afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:21:47Z"
    - latency: 2.882845ms
      message: 'load-balancer-api-external: tcp connection to afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:20:47Z"
    - latency: 7.32265ms
      message: 'load-balancer-api-external: resolved host name afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:20:47Z"
    - latency: 4.635024ms
      message: 'load-balancer-api-external: tcp connection to afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:19:47Z"
    - latency: 6.277267ms
      message: 'load-balancer-api-external: resolved host name afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:19:47Z"
    - latency: 5.760345ms
      message: 'load-balancer-api-external: tcp connection to afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:18:47Z"
    - latency: 6.522794ms
      message: 'load-balancer-api-external: resolved host name afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:18:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T09:46:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-247-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-247.ec2.internal
      uid: 3e224d11-06f7-43fa-9f97-8c2ca46726c8
    resourceVersion: "68303"
    uid: 670b9d15-2481-40c5-8769-6f0f0b48b43a
  spec:
    sourcePod: network-check-source-6f8b768455-lzhmx
    targetEndpoint: afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T09:52:47Z"
      message: 'load-balancer-api-internal: tcp connection to afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.962924ms
      message: 'load-balancer-api-internal: tcp connection to afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:22:47Z"
    - latency: 7.821497ms
      message: 'load-balancer-api-internal: resolved host name afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:22:47Z"
    - latency: 5.661543ms
      message: 'load-balancer-api-internal: tcp connection to afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:21:47Z"
    - latency: 7.189433ms
      message: 'load-balancer-api-internal: resolved host name afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:21:47Z"
    - latency: 3.893993ms
      message: 'load-balancer-api-internal: tcp connection to afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:20:47Z"
    - latency: 7.282661ms
      message: 'load-balancer-api-internal: resolved host name afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:20:47Z"
    - latency: 4.617277ms
      message: 'load-balancer-api-internal: tcp connection to afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:19:47Z"
    - latency: 6.35142ms
      message: 'load-balancer-api-internal: resolved host name afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:19:47Z"
    - latency: 5.754336ms
      message: 'load-balancer-api-internal: tcp connection to afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:18:47Z"
    - latency: 6.464259ms
      message: 'load-balancer-api-internal: resolved host name afe91909320da461281249afb56fa0f8-76af019de79df5e7.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:18:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T09:46:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-247-to-network-check-target-ip-10-0-132-247
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-247.ec2.internal
      uid: 3e224d11-06f7-43fa-9f97-8c2ca46726c8
    resourceVersion: "67225"
    uid: 972eadbd-1525-4a6e-9ab2-40c9fb9391c9
  spec:
    sourcePod: network-check-source-6f8b768455-lzhmx
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T09:53:47Z"
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.132403ms
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:21:47Z"
    - latency: 978.6µs
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:20:47Z"
    - latency: 1.255679ms
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:19:47Z"
    - latency: 972.129µs
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:18:47Z"
    - latency: 981.353µs
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:17:47Z"
    - latency: 1.331072ms
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:16:47Z"
    - latency: 911.444µs
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:15:47Z"
    - latency: 1.034927ms
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:14:47Z"
    - latency: 947.252µs
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:13:47Z"
    - latency: 1.571666ms
      message: 'network-check-target-ip-10-0-132-247: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:12:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T09:46:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-247-to-network-check-target-ip-10-0-132-4
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-247.ec2.internal
      uid: 3e224d11-06f7-43fa-9f97-8c2ca46726c8
    resourceVersion: "67227"
    uid: 638cd422-e307-42e4-922b-b7c29d426d51
  spec:
    sourcePod: network-check-source-6f8b768455-lzhmx
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T09:53:47Z"
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.599961ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:21:47Z"
    - latency: 2.506157ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:20:47Z"
    - latency: 2.438261ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:19:47Z"
    - latency: 2.552512ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:18:47Z"
    - latency: 2.402618ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:17:47Z"
    - latency: 2.372064ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:16:47Z"
    - latency: 2.623411ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:15:47Z"
    - latency: 2.8765ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:14:47Z"
    - latency: 2.623415ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:13:47Z"
    - latency: 2.590679ms
      message: 'network-check-target-ip-10-0-132-4: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:12:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T09:46:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-247-to-network-check-target-ip-10-0-135-40
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-247.ec2.internal
      uid: 3e224d11-06f7-43fa-9f97-8c2ca46726c8
    resourceVersion: "67226"
    uid: 9a8f6143-6b17-4a7d-818a-9ea8050a55bc
  spec:
    sourcePod: network-check-source-6f8b768455-lzhmx
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T09:53:47Z"
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.0071ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:21:47Z"
    - latency: 2.086965ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:20:47Z"
    - latency: 2.387144ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:19:47Z"
    - latency: 2.292391ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:18:47Z"
    - latency: 2.303296ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:17:47Z"
    - latency: 2.1306ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:16:47Z"
    - latency: 2.503961ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:15:47Z"
    - latency: 2.797231ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:14:47Z"
    - latency: 2.398365ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:13:47Z"
    - latency: 2.731425ms
      message: 'network-check-target-ip-10-0-135-40: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:12:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-14T09:46:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-247-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-247.ec2.internal
      uid: 3e224d11-06f7-43fa-9f97-8c2ca46726c8
    resourceVersion: "68300"
    uid: 4a943da1-1322-4d56-accb-db1355e3a3c1
  spec:
    sourcePod: network-check-source-6f8b768455-lzhmx
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-14T09:52:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.230543ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:22:47Z"
    - latency: 1.887545ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:22:47Z"
    - latency: 1.055556ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:21:47Z"
    - latency: 2.116106ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:21:47Z"
    - latency: 1.138341ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:20:47Z"
    - latency: 1.951037ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:20:47Z"
    - latency: 998.825µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:19:47Z"
    - latency: 1.762531ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:19:47Z"
    - latency: 860.465µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-14T10:18:47Z"
    - latency: 1.764052ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-14T10:18:47Z"
kind: List
metadata:
  resourceVersion: ""