apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:43:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-8-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-8.ec2.internal
      uid: 17e09243-bef8-49a5-8049-fc06382999a5
    resourceVersion: "38882"
    uid: 661a84d4-cada-4209-b486-c30baa64b608
  spec:
    sourcePod: network-check-source-869dcfcdcd-bqkh9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:50:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.19675ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:39:26Z"
    - latency: 972.405µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:38:26Z"
    - latency: 978.406µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:37:26Z"
    - latency: 1.06294ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:36:26Z"
    - latency: 1.050564ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:35:26Z"
    - latency: 926.079µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:34:26Z"
    - latency: 967.274µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:33:26Z"
    - latency: 1.122494ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:32:26Z"
    - latency: 910.794µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:31:26Z"
    - latency: 1.143681ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:43:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-8-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-8.ec2.internal
      uid: 17e09243-bef8-49a5-8049-fc06382999a5
    resourceVersion: "40910"
    uid: 28e8de08-42fd-481b-80bb-0d1ad91daa74
  spec:
    sourcePod: network-check-source-869dcfcdcd-bqkh9
    targetEndpoint: a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:49:26Z"
      message: 'load-balancer-api-external: tcp connection to a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.13174ms
      message: 'load-balancer-api-external: tcp connection to a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:43:26Z"
    - latency: 8.386407ms
      message: 'load-balancer-api-external: resolved host name a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:43:26Z"
    - latency: 5.318389ms
      message: 'load-balancer-api-external: tcp connection to a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:42:26Z"
    - latency: 7.184454ms
      message: 'load-balancer-api-external: resolved host name a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:42:26Z"
    - latency: 6.497114ms
      message: 'load-balancer-api-external: tcp connection to a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:41:26Z"
    - latency: 7.584367ms
      message: 'load-balancer-api-external: resolved host name a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:41:26Z"
    - latency: 6.109405ms
      message: 'load-balancer-api-external: tcp connection to a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:40:26Z"
    - latency: 12.02881ms
      message: 'load-balancer-api-external: resolved host name a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:40:26Z"
    - latency: 5.545519ms
      message: 'load-balancer-api-external: tcp connection to a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:39:26Z"
    - latency: 9.183775ms
      message: 'load-balancer-api-external: resolved host name a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:39:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:43:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-8-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-8.ec2.internal
      uid: 17e09243-bef8-49a5-8049-fc06382999a5
    resourceVersion: "40911"
    uid: 41f618fc-b120-48fb-906b-a247d3b4b0bd
  spec:
    sourcePod: network-check-source-869dcfcdcd-bqkh9
    targetEndpoint: a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:49:26Z"
      message: 'load-balancer-api-internal: tcp connection to a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.298821ms
      message: 'load-balancer-api-internal: tcp connection to a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:43:26Z"
    - latency: 8.356466ms
      message: 'load-balancer-api-internal: resolved host name a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:43:26Z"
    - latency: 4.450966ms
      message: 'load-balancer-api-internal: tcp connection to a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:42:26Z"
    - latency: 7.152244ms
      message: 'load-balancer-api-internal: resolved host name a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:42:26Z"
    - latency: 6.519688ms
      message: 'load-balancer-api-internal: tcp connection to a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:41:26Z"
    - latency: 7.534869ms
      message: 'load-balancer-api-internal: resolved host name a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:41:26Z"
    - latency: 6.102777ms
      message: 'load-balancer-api-internal: tcp connection to a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:40:26Z"
    - latency: 12.137846ms
      message: 'load-balancer-api-internal: resolved host name a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:40:26Z"
    - latency: 5.55331ms
      message: 'load-balancer-api-internal: tcp connection to a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:39:26Z"
    - latency: 9.119555ms
      message: 'load-balancer-api-internal: resolved host name a25538004c3f0420f875e4601a03567d-b9f588139c81e222.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:39:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:43:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-8-to-network-check-target-ip-10-0-132-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-8.ec2.internal
      uid: 17e09243-bef8-49a5-8049-fc06382999a5
    resourceVersion: "38879"
    uid: 8a2cf229-5f7f-4a40-ad5c-61641ffc3ce5
  spec:
    sourcePod: network-check-source-869dcfcdcd-bqkh9
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:50:26Z"
      message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 925.817µs
      message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:39:26Z"
    - latency: 911.473µs
      message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:38:26Z"
    - latency: 1.176049ms
      message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:37:26Z"
    - latency: 1.013464ms
      message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:36:26Z"
    - latency: 937.272µs
      message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:35:26Z"
    - latency: 772.028µs
      message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:34:26Z"
    - latency: 918.064µs
      message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:33:26Z"
    - latency: 1.062532ms
      message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:32:26Z"
    - latency: 928.528µs
      message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:31:26Z"
    - latency: 949.973µs
      message: 'network-check-target-ip-10-0-132-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:43:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-8-to-network-check-target-ip-10-0-137-86
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-8.ec2.internal
      uid: 17e09243-bef8-49a5-8049-fc06382999a5
    resourceVersion: "38881"
    uid: d245e6b9-6dba-4853-a49f-0675640e45b5
  spec:
    sourcePod: network-check-source-869dcfcdcd-bqkh9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:50:26Z"
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.433826ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:39:26Z"
    - latency: 2.681441ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:38:26Z"
    - latency: 2.494006ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:37:26Z"
    - latency: 2.299437ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:36:26Z"
    - latency: 2.437599ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:35:26Z"
    - latency: 2.003556ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:34:26Z"
    - latency: 2.336709ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:33:26Z"
    - latency: 2.181505ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:32:26Z"
    - latency: 2.609603ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:31:26Z"
    - latency: 2.603637ms
      message: 'network-check-target-ip-10-0-137-86: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:43:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-8-to-network-check-target-ip-10-0-140-163
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-8.ec2.internal
      uid: 17e09243-bef8-49a5-8049-fc06382999a5
    resourceVersion: "38880"
    uid: 76559a7b-f863-48bd-877b-cfa2e98be033
  spec:
    sourcePod: network-check-source-869dcfcdcd-bqkh9
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:50:26Z"
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.24922ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:39:26Z"
    - latency: 2.200867ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:38:26Z"
    - latency: 2.136502ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:37:26Z"
    - latency: 2.794844ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:36:26Z"
    - latency: 2.199401ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:35:26Z"
    - latency: 2.651159ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:34:26Z"
    - latency: 2.058982ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:33:26Z"
    - latency: 2.142783ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:32:26Z"
    - latency: 2.124552ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:31:26Z"
    - latency: 2.268832ms
      message: 'network-check-target-ip-10-0-140-163: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:30:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T18:43:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-8-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-8.ec2.internal
      uid: 17e09243-bef8-49a5-8049-fc06382999a5
    resourceVersion: "40909"
    uid: eaba6f40-561f-4cc7-9511-2b246b2f1717
  spec:
    sourcePod: network-check-source-869dcfcdcd-bqkh9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T18:49:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 958.176µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:43:26Z"
    - latency: 1.778809ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:43:26Z"
    - latency: 1.090924ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:42:26Z"
    - latency: 1.922488ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:42:26Z"
    - latency: 1.194789ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:41:26Z"
    - latency: 1.676265ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:41:26Z"
    - latency: 939.526µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:40:26Z"
    - latency: 1.71792ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:40:26Z"
    - latency: 1.159919ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T19:39:26Z"
    - latency: 2.167456ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T19:39:26Z"
kind: List
metadata:
  resourceVersion: ""