apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:50:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: 6366f275-0534-4d98-81a4-daffd8211bcd
    resourceVersion: "54098"
    uid: 4a3503bf-e545-46a5-8be3-fc13d3761e5b
  spec:
    sourcePod: network-check-source-989f8b8dc-6c9h9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:57:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.823235ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:25:48Z"
    - latency: 1.250982ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:24:48Z"
    - latency: 1.240563ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:23:48Z"
    - latency: 893.943µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:22:48Z"
    - latency: 1.072421ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:21:48Z"
    - latency: 835.603µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:20:48Z"
    - latency: 968.151µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:19:48Z"
    - latency: 1.295895ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:18:48Z"
    - latency: 1.565142ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:17:48Z"
    - latency: 904.862µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:16:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:50:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: 6366f275-0534-4d98-81a4-daffd8211bcd
    resourceVersion: "55066"
    uid: 72051718-727a-4e55-9801-74a337769ddc
  spec:
    sourcePod: network-check-source-989f8b8dc-6c9h9
    targetEndpoint: a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:56:48Z"
      message: 'load-balancer-api-external: tcp connection to a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.037859ms
      message: 'load-balancer-api-external: tcp connection to a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:26:48Z"
    - latency: 7.500509ms
      message: 'load-balancer-api-external: resolved host name a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:26:48Z"
    - latency: 5.090651ms
      message: 'load-balancer-api-external: tcp connection to a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:25:48Z"
    - latency: 7.699452ms
      message: 'load-balancer-api-external: resolved host name a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:25:48Z"
    - latency: 3.993864ms
      message: 'load-balancer-api-external: tcp connection to a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:24:48Z"
    - latency: 7.87205ms
      message: 'load-balancer-api-external: resolved host name a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:24:48Z"
    - latency: 5.244073ms
      message: 'load-balancer-api-external: tcp connection to a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:23:48Z"
    - latency: 8.150731ms
      message: 'load-balancer-api-external: resolved host name a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:23:48Z"
    - latency: 5.050985ms
      message: 'load-balancer-api-external: tcp connection to a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:22:48Z"
    - latency: 6.744872ms
      message: 'load-balancer-api-external: resolved host name a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:22:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:50:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: 6366f275-0534-4d98-81a4-daffd8211bcd
    resourceVersion: "55065"
    uid: c3d45712-4f6c-456c-8354-1500a98f261b
  spec:
    sourcePod: network-check-source-989f8b8dc-6c9h9
    targetEndpoint: a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:56:48Z"
      message: 'load-balancer-api-internal: tcp connection to a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.978991ms
      message: 'load-balancer-api-internal: tcp connection to a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:26:48Z"
    - latency: 7.473987ms
      message: 'load-balancer-api-internal: resolved host name a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:26:48Z"
    - latency: 5.124255ms
      message: 'load-balancer-api-internal: tcp connection to a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:25:48Z"
    - latency: 7.649502ms
      message: 'load-balancer-api-internal: resolved host name a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:25:48Z"
    - latency: 4.543958ms
      message: 'load-balancer-api-internal: tcp connection to a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:24:48Z"
    - latency: 7.80903ms
      message: 'load-balancer-api-internal: resolved host name a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:24:48Z"
    - latency: 5.183648ms
      message: 'load-balancer-api-internal: tcp connection to a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:23:48Z"
    - latency: 8.118579ms
      message: 'load-balancer-api-internal: resolved host name a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:23:48Z"
    - latency: 5.083629ms
      message: 'load-balancer-api-internal: tcp connection to a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:22:48Z"
    - latency: 6.706388ms
      message: 'load-balancer-api-internal: resolved host name a7439d258ed15464b8a664858a9558ba-ba81b561f5ffb766.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:22:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:50:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-network-check-target-ip-10-0-131-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: 6366f275-0534-4d98-81a4-daffd8211bcd
    resourceVersion: "54096"
    uid: 316bd6c7-239e-4c62-b7bc-d8f11b3df9d8
  spec:
    sourcePod: network-check-source-989f8b8dc-6c9h9
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:57:48Z"
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.137673ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:25:48Z"
    - latency: 1.332753ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:24:48Z"
    - latency: 1.363273ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:23:48Z"
    - latency: 937.823µs
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:22:48Z"
    - latency: 1.223743ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:21:48Z"
    - latency: 1.3801ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:20:48Z"
    - latency: 2.074727ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:19:48Z"
    - latency: 1.995442ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:18:48Z"
    - latency: 1.040693ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:17:48Z"
    - latency: 1.422132ms
      message: 'network-check-target-ip-10-0-131-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:16:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:50:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-network-check-target-ip-10-0-134-116
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: 6366f275-0534-4d98-81a4-daffd8211bcd
    resourceVersion: "54095"
    uid: dac48dc6-2a76-41ae-9b19-a03800cc7ab9
  spec:
    sourcePod: network-check-source-989f8b8dc-6c9h9
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:57:48Z"
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.727145ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:25:48Z"
    - latency: 2.25524ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:24:48Z"
    - latency: 2.62871ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:23:48Z"
    - latency: 2.422021ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:22:48Z"
    - latency: 2.639757ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:21:48Z"
    - latency: 2.389055ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:20:48Z"
    - latency: 2.387436ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:19:48Z"
    - latency: 2.50682ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:18:48Z"
    - latency: 2.238162ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:17:48Z"
    - latency: 2.091442ms
      message: 'network-check-target-ip-10-0-134-116: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:16:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:50:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-network-check-target-ip-10-0-142-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: 6366f275-0534-4d98-81a4-daffd8211bcd
    resourceVersion: "54097"
    uid: 68b98b36-d2a5-477d-bdf0-a35d8925943e
  spec:
    sourcePod: network-check-source-989f8b8dc-6c9h9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:57:48Z"
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.674062ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:25:48Z"
    - latency: 2.372812ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:24:48Z"
    - latency: 2.270459ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:23:48Z"
    - latency: 2.321426ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:22:48Z"
    - latency: 2.502949ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:21:48Z"
    - latency: 2.467324ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:20:48Z"
    - latency: 2.549923ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:19:48Z"
    - latency: 2.790019ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:18:48Z"
    - latency: 2.463892ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:17:48Z"
    - latency: 2.135051ms
      message: 'network-check-target-ip-10-0-142-117: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:16:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T22:50:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-131-21-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-131-21.ec2.internal
      uid: 6366f275-0534-4d98-81a4-daffd8211bcd
    resourceVersion: "55064"
    uid: b3a7ad5c-8ffb-42d8-a891-8994ea6fd37e
  spec:
    sourcePod: network-check-source-989f8b8dc-6c9h9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T22:56:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 852.955µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:26:48Z"
    - latency: 1.815095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:26:48Z"
    - latency: 964.691µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:25:48Z"
    - latency: 1.969669ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:25:48Z"
    - latency: 1.004401ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:24:48Z"
    - latency: 2.371806ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:24:48Z"
    - latency: 856.486µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:23:48Z"
    - latency: 1.829728ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:23:48Z"
    - latency: 912.742µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T23:22:48Z"
    - latency: 1.791511ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T23:22:48Z"
kind: List
metadata:
  resourceVersion: ""