apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:31:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-166-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-166.ec2.internal
      uid: 34bee279-bca4-4532-9c83-9a3367066d8c
    resourceVersion: "63952"
    uid: 4dfb4525-f1f9-432c-acd8-c95b941f0030
  spec:
    sourcePod: network-check-source-7d88cb55d8-v664j
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:38:56Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.155191ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:20:56Z"
    - latency: 838.719µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:19:56Z"
    - latency: 2.2388ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:18:56Z"
    - latency: 1.670293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:17:56Z"
    - latency: 1.036499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:16:56Z"
    - latency: 1.0905ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:15:56Z"
    - latency: 943.648µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:14:56Z"
    - latency: 862.12µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:13:56Z"
    - latency: 1.155764ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:12:56Z"
    - latency: 1.007683ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:11:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:31:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-166-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-166.ec2.internal
      uid: 34bee279-bca4-4532-9c83-9a3367066d8c
    resourceVersion: "62982"
    uid: 34bd8965-2bf1-4386-b243-bed7c152f9b1
  spec:
    sourcePod: network-check-source-7d88cb55d8-v664j
    targetEndpoint: ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:37:56Z"
      message: 'load-balancer-api-external: tcp connection to ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.076611ms
      message: 'load-balancer-api-external: tcp connection to ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:19:56Z"
    - latency: 6.854958ms
      message: 'load-balancer-api-external: resolved host name ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:19:56Z"
    - latency: 4.765714ms
      message: 'load-balancer-api-external: tcp connection to ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:18:56Z"
    - latency: 16.241546ms
      message: 'load-balancer-api-external: resolved host name ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:18:56Z"
    - latency: 5.445551ms
      message: 'load-balancer-api-external: tcp connection to ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:17:56Z"
    - latency: 6.418238ms
      message: 'load-balancer-api-external: resolved host name ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:17:56Z"
    - latency: 5.7815ms
      message: 'load-balancer-api-external: tcp connection to ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:16:56Z"
    - latency: 6.702146ms
      message: 'load-balancer-api-external: resolved host name ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:16:56Z"
    - latency: 5.473897ms
      message: 'load-balancer-api-external: tcp connection to ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:15:56Z"
    - latency: 6.276051ms
      message: 'load-balancer-api-external: resolved host name ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:15:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:31:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-166-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-166.ec2.internal
      uid: 34bee279-bca4-4532-9c83-9a3367066d8c
    resourceVersion: "62983"
    uid: 1f4b206d-d691-4f6c-88e0-b975cba9b9ed
  spec:
    sourcePod: network-check-source-7d88cb55d8-v664j
    targetEndpoint: ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:37:56Z"
      message: 'load-balancer-api-internal: tcp connection to ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.989144ms
      message: 'load-balancer-api-internal: tcp connection to ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:19:56Z"
    - latency: 6.766438ms
      message: 'load-balancer-api-internal: resolved host name ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:19:56Z"
    - latency: 5.086472ms
      message: 'load-balancer-api-internal: tcp connection to ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:18:56Z"
    - latency: 17.257615ms
      message: 'load-balancer-api-internal: resolved host name ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:18:56Z"
    - latency: 5.487193ms
      message: 'load-balancer-api-internal: tcp connection to ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:17:56Z"
    - latency: 5.887625ms
      message: 'load-balancer-api-internal: resolved host name ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:17:56Z"
    - latency: 4.953222ms
      message: 'load-balancer-api-internal: tcp connection to ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:16:56Z"
    - latency: 6.725566ms
      message: 'load-balancer-api-internal: resolved host name ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:16:56Z"
    - latency: 4.018664ms
      message: 'load-balancer-api-internal: tcp connection to ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:15:56Z"
    - latency: 6.174838ms
      message: 'load-balancer-api-internal: resolved host name ad6c3426588844ca4b596f6951980b33-75ca46b1d5b50857.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:15:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:31:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-166-to-network-check-target-ip-10-0-131-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-166.ec2.internal
      uid: 34bee279-bca4-4532-9c83-9a3367066d8c
    resourceVersion: "63949"
    uid: e0f4f78f-79f4-460c-b5cd-a786f0f58384
  spec:
    sourcePod: network-check-source-7d88cb55d8-v664j
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:38:56Z"
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.073589ms
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:20:56Z"
    - latency: 736.219µs
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:19:56Z"
    - latency: 4.235816ms
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:18:56Z"
    - latency: 961.723µs
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:17:56Z"
    - latency: 897.492µs
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:16:56Z"
    - latency: 1.319103ms
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:15:56Z"
    - latency: 845.544µs
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:14:56Z"
    - latency: 873.503µs
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:13:56Z"
    - latency: 952.409µs
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:12:56Z"
    - latency: 1.061812ms
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:11:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:31:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-166-to-network-check-target-ip-10-0-131-59
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-166.ec2.internal
      uid: 34bee279-bca4-4532-9c83-9a3367066d8c
    resourceVersion: "63950"
    uid: 917f0cd6-a5c7-4d35-9a06-f63d0978fe62
  spec:
    sourcePod: network-check-source-7d88cb55d8-v664j
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:38:56Z"
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.518981ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:20:56Z"
    - latency: 2.451976ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:19:56Z"
    - latency: 2.857588ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:18:56Z"
    - latency: 2.688674ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:17:56Z"
    - latency: 2.523464ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:16:56Z"
    - latency: 2.451009ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:15:56Z"
    - latency: 2.325818ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:14:56Z"
    - latency: 2.275527ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:13:56Z"
    - latency: 2.561941ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:12:56Z"
    - latency: 2.310915ms
      message: 'network-check-target-ip-10-0-131-59: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:11:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:31:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-166-to-network-check-target-ip-10-0-136-113
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-166.ec2.internal
      uid: 34bee279-bca4-4532-9c83-9a3367066d8c
    resourceVersion: "63951"
    uid: 9465c69d-54b5-4afb-9cd7-22316b92204f
  spec:
    sourcePod: network-check-source-7d88cb55d8-v664j
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:38:56Z"
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.457203ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:20:56Z"
    - latency: 2.179126ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:19:56Z"
    - latency: 2.531389ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:18:56Z"
    - latency: 2.085584ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:17:56Z"
    - latency: 2.424198ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:16:56Z"
    - latency: 2.217955ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:15:56Z"
    - latency: 2.147028ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:14:56Z"
    - latency: 1.831803ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:13:56Z"
    - latency: 2.520559ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:12:56Z"
    - latency: 2.507099ms
      message: 'network-check-target-ip-10-0-136-113: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:11:56Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-27T19:31:55Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-166-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-166.ec2.internal
      uid: 34bee279-bca4-4532-9c83-9a3367066d8c
    resourceVersion: "62981"
    uid: f9afffe4-3575-4cb0-a79b-8f3eca93d771
  spec:
    sourcePod: network-check-source-7d88cb55d8-v664j
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-27T19:37:56Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.153835ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:19:56Z"
    - latency: 2.120464ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:19:56Z"
    - latency: 4.102062ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:18:56Z"
    - latency: 6.016733ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:18:56Z"
    - latency: 930.569µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:17:56Z"
    - latency: 1.776505ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:17:56Z"
    - latency: 905.853µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:16:56Z"
    - latency: 1.686056ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:16:56Z"
    - latency: 1.003344ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-27T20:15:56Z"
    - latency: 1.747077ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-27T20:15:56Z"
kind: List
metadata:
  resourceVersion: ""