apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:20:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-160-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-160.ec2.internal
      uid: 93e98b4e-a44c-4cb8-9a6c-026125ea3c56
    resourceVersion: "22487"
    uid: 274ec299-f107-41c5-928a-4406ab6dccc9
  spec:
    sourcePod: network-check-source-8894fc9bd-sgd2m
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:27: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.515001ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:34:26Z"
    - latency: 986.492µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:33:26Z"
    - latency: 851.104µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:32:26Z"
    - latency: 1.011912ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:31:26Z"
    - latency: 955.074µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:30:26Z"
    - latency: 844.358µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:29:26Z"
    - latency: 1.262431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:28:26Z"
    - latency: 865.981µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:27:26Z"
    - latency: 771.649µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:26:26Z"
    - latency: 987.302µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:25:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:20:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-160-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-160.ec2.internal
      uid: 93e98b4e-a44c-4cb8-9a6c-026125ea3c56
    resourceVersion: "25724"
    uid: c38a036f-3d6e-47cf-94c4-bdfc6c578edf
  spec:
    sourcePod: network-check-source-8894fc9bd-sgd2m
    targetEndpoint: a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:26:26Z"
      message: 'load-balancer-api-external: tcp connection to a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.950856ms
      message: 'load-balancer-api-external: tcp connection to a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:38:26Z"
    - latency: 7.778444ms
      message: 'load-balancer-api-external: resolved host name a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:38:26Z"
    - latency: 4.888269ms
      message: 'load-balancer-api-external: tcp connection to a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:37:26Z"
    - latency: 8.165467ms
      message: 'load-balancer-api-external: resolved host name a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:37:26Z"
    - latency: 4.371017ms
      message: 'load-balancer-api-external: tcp connection to a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:36:26Z"
    - latency: 8.839908ms
      message: 'load-balancer-api-external: resolved host name a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:36:26Z"
    - latency: 5.357657ms
      message: 'load-balancer-api-external: tcp connection to a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:35:26Z"
    - latency: 9.630727ms
      message: 'load-balancer-api-external: resolved host name a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:35:26Z"
    - latency: 5.872034ms
      message: 'load-balancer-api-external: tcp connection to a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:34:26Z"
    - latency: 8.364221ms
      message: 'load-balancer-api-external: resolved host name a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:34:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:20:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-160-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-160.ec2.internal
      uid: 93e98b4e-a44c-4cb8-9a6c-026125ea3c56
    resourceVersion: "25723"
    uid: 3e80faf3-7240-406e-92aa-58e443eae156
  spec:
    sourcePod: network-check-source-8894fc9bd-sgd2m
    targetEndpoint: a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:26:26Z"
      message: 'load-balancer-api-internal: tcp connection to a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.893443ms
      message: 'load-balancer-api-internal: tcp connection to a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:38:26Z"
    - latency: 7.91758ms
      message: 'load-balancer-api-internal: resolved host name a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:38:26Z"
    - latency: 4.880898ms
      message: 'load-balancer-api-internal: tcp connection to a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:37:26Z"
    - latency: 8.204008ms
      message: 'load-balancer-api-internal: resolved host name a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:37:26Z"
    - latency: 5.474637ms
      message: 'load-balancer-api-internal: tcp connection to a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:36:26Z"
    - latency: 8.899189ms
      message: 'load-balancer-api-internal: resolved host name a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:36:26Z"
    - latency: 5.38486ms
      message: 'load-balancer-api-internal: tcp connection to a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:35:26Z"
    - latency: 9.682258ms
      message: 'load-balancer-api-internal: resolved host name a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:35:26Z"
    - latency: 6.924115ms
      message: 'load-balancer-api-internal: tcp connection to a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:34:26Z"
    - latency: 8.420648ms
      message: 'load-balancer-api-internal: resolved host name a31d1381622a54f8db281d47d387b830-9c8b0e1853e8223d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:34:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:20:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-160-to-network-check-target-ip-10-0-132-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-160.ec2.internal
      uid: 93e98b4e-a44c-4cb8-9a6c-026125ea3c56
    resourceVersion: "22484"
    uid: 19bf236b-786b-4fee-9633-96f2a36732bf
  spec:
    sourcePod: network-check-source-8894fc9bd-sgd2m
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:27:26Z"
      message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 744.065µs
      message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:34:26Z"
    - latency: 732.646µs
      message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:33:26Z"
    - latency: 787.085µs
      message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:32:26Z"
    - latency: 762.654µs
      message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:31:26Z"
    - latency: 752.099µs
      message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:30:26Z"
    - latency: 1.305197ms
      message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:29:26Z"
    - latency: 809.751µs
      message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:28:26Z"
    - latency: 932.555µs
      message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:27:26Z"
    - latency: 850.077µs
      message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:26:26Z"
    - latency: 1.022978ms
      message: 'network-check-target-ip-10-0-132-160: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:25:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:20:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-160-to-network-check-target-ip-10-0-134-36
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-160.ec2.internal
      uid: 93e98b4e-a44c-4cb8-9a6c-026125ea3c56
    resourceVersion: "22486"
    uid: fd55810b-8187-4d4c-9a27-b02d46a319df
  spec:
    sourcePod: network-check-source-8894fc9bd-sgd2m
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:27:26Z"
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.211071ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:34:26Z"
    - latency: 2.179716ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:33:26Z"
    - latency: 1.80279ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:32:26Z"
    - latency: 2.084457ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:31:26Z"
    - latency: 2.092467ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:30:26Z"
    - latency: 2.127523ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:29:26Z"
    - latency: 2.33579ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:28:26Z"
    - latency: 2.268191ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:27:26Z"
    - latency: 2.2386ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:26:26Z"
    - latency: 2.184647ms
      message: 'network-check-target-ip-10-0-134-36: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:25:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:20:24Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-160-to-network-check-target-ip-10-0-138-119
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-160.ec2.internal
      uid: 93e98b4e-a44c-4cb8-9a6c-026125ea3c56
    resourceVersion: "22485"
    uid: a3c683d0-929c-441c-9f4f-1a220282a80f
  spec:
    sourcePod: network-check-source-8894fc9bd-sgd2m
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:27:26Z"
      message: 'network-check-target-ip-10-0-138-119: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.841776ms
      message: 'network-check-target-ip-10-0-138-119: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:34:26Z"
    - latency: 1.578473ms
      message: 'network-check-target-ip-10-0-138-119: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:33:26Z"
    - latency: 1.703881ms
      message: 'network-check-target-ip-10-0-138-119: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:32:26Z"
    - latency: 1.713328ms
      message: 'network-check-target-ip-10-0-138-119: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:31:26Z"
    - latency: 1.610616ms
      message: 'network-check-target-ip-10-0-138-119: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:30:26Z"
    - latency: 1.516835ms
      message: 'network-check-target-ip-10-0-138-119: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:29:26Z"
    - latency: 1.648927ms
      message: 'network-check-target-ip-10-0-138-119: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:28:26Z"
    - latency: 1.866126ms
      message: 'network-check-target-ip-10-0-138-119: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:27:26Z"
    - latency: 1.648367ms
      message: 'network-check-target-ip-10-0-138-119: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:26:26Z"
    - latency: 1.816218ms
      message: 'network-check-target-ip-10-0-138-119: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:25:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-28T19:20:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-160-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-160.ec2.internal
      uid: 93e98b4e-a44c-4cb8-9a6c-026125ea3c56
    resourceVersion: "25722"
    uid: bc95b292-69ba-46a1-a8cc-7ebc3d356ad4
  spec:
    sourcePod: network-check-source-8894fc9bd-sgd2m
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-28T19:26:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 859.339µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:38:26Z"
    - latency: 1.664731ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:38:26Z"
    - latency: 1.100353ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:37:26Z"
    - latency: 1.677384ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:37:26Z"
    - latency: 834.085µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:36:26Z"
    - latency: 2.040278ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:36:26Z"
    - latency: 722.811µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:35:26Z"
    - latency: 2.602361ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:35:26Z"
    - latency: 1.005905ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-28T19:34:26Z"
    - latency: 2.14935ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-28T19:34:26Z"
kind: List
metadata:
  resourceVersion: ""