apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T20:15:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-41-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-41.ec2.internal
      uid: a3fa484c-047f-4cea-83a5-69179e4fdbbf
    resourceVersion: "31829"
    uid: c8e88b71-adb7-4b43-9e78-655e16c65780
  spec:
    sourcePod: network-check-source-8894fc9bd-gvgs9
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:22:41Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.0765ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:57:41Z"
    - latency: 1.019066ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:56:41Z"
    - latency: 1.330881ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:55:41Z"
    - latency: 988.256µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:54:41Z"
    - latency: 943.254µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:53:41Z"
    - latency: 1.294922ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:52:41Z"
    - latency: 1.081826ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:51:41Z"
    - latency: 1.136701ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:50:41Z"
    - latency: 955.193µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:49:41Z"
    - latency: 930.834µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:48:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T20:15:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-41-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-41.ec2.internal
      uid: a3fa484c-047f-4cea-83a5-69179e4fdbbf
    resourceVersion: "31830"
    uid: 79f6fbba-af44-4692-91bc-af53696d9382
  spec:
    sourcePod: network-check-source-8894fc9bd-gvgs9
    targetEndpoint: a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:21:41Z"
      message: 'load-balancer-api-external: tcp connection to a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.060709ms
      message: 'load-balancer-api-external: tcp connection to a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:57:41Z"
    - latency: 8.87233ms
      message: 'load-balancer-api-external: resolved host name a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:57:41Z"
    - latency: 4.665322ms
      message: 'load-balancer-api-external: tcp connection to a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:56:41Z"
    - latency: 12.490807ms
      message: 'load-balancer-api-external: resolved host name a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:56:41Z"
    - latency: 4.219749ms
      message: 'load-balancer-api-external: tcp connection to a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:55:41Z"
    - latency: 8.747024ms
      message: 'load-balancer-api-external: resolved host name a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:55:41Z"
    - latency: 3.866642ms
      message: 'load-balancer-api-external: tcp connection to a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:54:41Z"
    - latency: 7.605847ms
      message: 'load-balancer-api-external: resolved host name a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:54:41Z"
    - latency: 4.806523ms
      message: 'load-balancer-api-external: tcp connection to a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:53:41Z"
    - latency: 11.126101ms
      message: 'load-balancer-api-external: resolved host name a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:53:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T20:15:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-41-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-41.ec2.internal
      uid: a3fa484c-047f-4cea-83a5-69179e4fdbbf
    resourceVersion: "31831"
    uid: d57a4590-63e6-4a28-90a5-8888c32d13e9
  spec:
    sourcePod: network-check-source-8894fc9bd-gvgs9
    targetEndpoint: a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:21:41Z"
      message: 'load-balancer-api-internal: tcp connection to a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.066231ms
      message: 'load-balancer-api-internal: tcp connection to a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:57:41Z"
    - latency: 8.726838ms
      message: 'load-balancer-api-internal: resolved host name a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:57:41Z"
    - latency: 4.313651ms
      message: 'load-balancer-api-internal: tcp connection to a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:56:41Z"
    - latency: 12.622727ms
      message: 'load-balancer-api-internal: resolved host name a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:56:41Z"
    - latency: 4.237413ms
      message: 'load-balancer-api-internal: tcp connection to a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:55:41Z"
    - latency: 8.68773ms
      message: 'load-balancer-api-internal: resolved host name a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:55:41Z"
    - latency: 3.806233ms
      message: 'load-balancer-api-internal: tcp connection to a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:54:41Z"
    - latency: 7.70828ms
      message: 'load-balancer-api-internal: resolved host name a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:54:41Z"
    - latency: 4.778355ms
      message: 'load-balancer-api-internal: tcp connection to a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:53:41Z"
    - latency: 11.034492ms
      message: 'load-balancer-api-internal: resolved host name a7cd9fe4669d04e2c85e74b08a7092ae-b0bfb60fa054c9f6.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:53:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T20:15:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-41-to-network-check-target-ip-10-0-129-41
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-41.ec2.internal
      uid: a3fa484c-047f-4cea-83a5-69179e4fdbbf
    resourceVersion: "31825"
    uid: 7bb21c3b-df63-4342-b856-b1d49a092781
  spec:
    sourcePod: network-check-source-8894fc9bd-gvgs9
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:22:41Z"
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 791.416µs
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:57:41Z"
    - latency: 795.589µs
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:56:41Z"
    - latency: 1.463027ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:55:41Z"
    - latency: 1.454916ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:54:41Z"
    - latency: 1.414359ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:53:41Z"
    - latency: 1.309578ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:52:41Z"
    - latency: 865.722µs
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:51:41Z"
    - latency: 869.177µs
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:50:41Z"
    - latency: 1.39839ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:49:41Z"
    - latency: 1.032975ms
      message: 'network-check-target-ip-10-0-129-41: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:48:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T20:15:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-41-to-network-check-target-ip-10-0-134-158
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-41.ec2.internal
      uid: a3fa484c-047f-4cea-83a5-69179e4fdbbf
    resourceVersion: "31826"
    uid: 8d2dc63a-3f45-4ccd-b048-887581f5f2c3
  spec:
    sourcePod: network-check-source-8894fc9bd-gvgs9
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:22:41Z"
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.953916ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:57:41Z"
    - latency: 1.764041ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:56:41Z"
    - latency: 1.913292ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:55:41Z"
    - latency: 1.8675ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:54:41Z"
    - latency: 1.928654ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:53:41Z"
    - latency: 1.941858ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:52:41Z"
    - latency: 2.004297ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:51:41Z"
    - latency: 1.82666ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:50:41Z"
    - latency: 1.903457ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:49:41Z"
    - latency: 1.92173ms
      message: 'network-check-target-ip-10-0-134-158: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:48:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T20:15:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-41-to-network-check-target-ip-10-0-135-182
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-41.ec2.internal
      uid: a3fa484c-047f-4cea-83a5-69179e4fdbbf
    resourceVersion: "31827"
    uid: 101b69d2-e0b1-4f55-a27c-2210924f19aa
  spec:
    sourcePod: network-check-source-8894fc9bd-gvgs9
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:22:41Z"
      message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.263763ms
      message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:57:41Z"
    - latency: 1.965443ms
      message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:56:41Z"
    - latency: 2.10205ms
      message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:55:41Z"
    - latency: 1.917008ms
      message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:54:41Z"
    - latency: 2.388533ms
      message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:53:41Z"
    - latency: 2.135846ms
      message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:52:41Z"
    - latency: 2.233181ms
      message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:51:41Z"
    - latency: 2.246854ms
      message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:50:41Z"
    - latency: 1.923767ms
      message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:49:41Z"
    - latency: 2.131199ms
      message: 'network-check-target-ip-10-0-135-182: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:48:41Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-16T20:15:39Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-41-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-41.ec2.internal
      uid: a3fa484c-047f-4cea-83a5-69179e4fdbbf
    resourceVersion: "31828"
    uid: e7c9856c-8f58-4a83-9c0d-5392a69c40b0
  spec:
    sourcePod: network-check-source-8894fc9bd-gvgs9
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-16T20:21:41Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 821.781µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:57:41Z"
    - latency: 1.934378ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:57:41Z"
    - latency: 666.091µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:56:41Z"
    - latency: 1.607821ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:56:41Z"
    - latency: 1.187238ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:55:41Z"
    - latency: 1.493835ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:55:41Z"
    - latency: 1.091819ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:54:41Z"
    - latency: 1.662034ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:54:41Z"
    - latency: 854.963µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-16T20:53:41Z"
    - latency: 1.879008ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-16T20:53:41Z"
kind: List
metadata:
  resourceVersion: ""