apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T13:37:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-33-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-33.ec2.internal
      uid: 77b011f4-2888-47fe-a7c6-241a72395dd3
    resourceVersion: "33961"
    uid: 44cc2961-ce27-4cd4-8131-ac9bd2daf6dd
  spec:
    sourcePod: network-check-source-8894fc9bd-7bc2w
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T13:44:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.298363ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:58:10Z"
    - latency: 1.193713ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:57:10Z"
    - latency: 1.208618ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:56:10Z"
    - latency: 893.381µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:55:10Z"
    - latency: 1.066447ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:54:10Z"
    - latency: 958.172µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:53:10Z"
    - latency: 998.094µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:52:10Z"
    - latency: 950.663µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:51:10Z"
    - latency: 994.668µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:50:10Z"
    - latency: 885.315µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:49:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T13:37:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-33-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-33.ec2.internal
      uid: 77b011f4-2888-47fe-a7c6-241a72395dd3
    resourceVersion: "36352"
    uid: c48170f3-dd8e-4f13-8081-73052999ee01
  spec:
    sourcePod: network-check-source-8894fc9bd-7bc2w
    targetEndpoint: a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T13:43:10Z"
      message: 'load-balancer-api-external: tcp connection to a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.86117ms
      message: 'load-balancer-api-external: tcp connection to a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:01:10Z"
    - latency: 8.698906ms
      message: 'load-balancer-api-external: resolved host name a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:01:10Z"
    - latency: 6.322824ms
      message: 'load-balancer-api-external: tcp connection to a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:00:10Z"
    - latency: 8.399526ms
      message: 'load-balancer-api-external: resolved host name a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:00:10Z"
    - latency: 5.161532ms
      message: 'load-balancer-api-external: tcp connection to a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:59:10Z"
    - latency: 8.603063ms
      message: 'load-balancer-api-external: resolved host name a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T13:59:10Z"
    - latency: 5.221257ms
      message: 'load-balancer-api-external: tcp connection to a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:58:10Z"
    - latency: 8.573701ms
      message: 'load-balancer-api-external: resolved host name a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T13:58:10Z"
    - latency: 5.410003ms
      message: 'load-balancer-api-external: tcp connection to a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:57:10Z"
    - latency: 8.175607ms
      message: 'load-balancer-api-external: resolved host name a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T13:57:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T13:37:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-33-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-33.ec2.internal
      uid: 77b011f4-2888-47fe-a7c6-241a72395dd3
    resourceVersion: "36353"
    uid: d30ba74b-bc00-47f2-b149-5977a0b52ad9
  spec:
    sourcePod: network-check-source-8894fc9bd-7bc2w
    targetEndpoint: a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T13:43:10Z"
      message: 'load-balancer-api-internal: tcp connection to a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.580124ms
      message: 'load-balancer-api-internal: tcp connection to a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:01:10Z"
    - latency: 8.711172ms
      message: 'load-balancer-api-internal: resolved host name a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:01:10Z"
    - latency: 6.292868ms
      message: 'load-balancer-api-internal: tcp connection to a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:00:10Z"
    - latency: 8.407744ms
      message: 'load-balancer-api-internal: resolved host name a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:00:10Z"
    - latency: 5.173512ms
      message: 'load-balancer-api-internal: tcp connection to a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:59:10Z"
    - latency: 8.531172ms
      message: 'load-balancer-api-internal: resolved host name a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T13:59:10Z"
    - latency: 5.222402ms
      message: 'load-balancer-api-internal: tcp connection to a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:58:10Z"
    - latency: 8.538025ms
      message: 'load-balancer-api-internal: resolved host name a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T13:58:10Z"
    - latency: 5.396723ms
      message: 'load-balancer-api-internal: tcp connection to a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:57:10Z"
    - latency: 8.093281ms
      message: 'load-balancer-api-internal: resolved host name a28131e89be4243348bd2f57e27446f1-2b19763d9b23c95c.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T13:57:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T13:37:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-33-to-network-check-target-ip-10-0-128-108
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-33.ec2.internal
      uid: 77b011f4-2888-47fe-a7c6-241a72395dd3
    resourceVersion: "33959"
    uid: 7f876f9e-7c48-4117-a7ff-7bc3c2c3bd38
  spec:
    sourcePod: network-check-source-8894fc9bd-7bc2w
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T13:44:10Z"
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.735185ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:58:10Z"
    - latency: 2.579269ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:57:10Z"
    - latency: 2.093484ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:56:10Z"
    - latency: 2.133879ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:55:10Z"
    - latency: 2.535464ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:54:10Z"
    - latency: 2.21335ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:53:10Z"
    - latency: 2.302959ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:52:10Z"
    - latency: 2.069703ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:51:10Z"
    - latency: 2.152463ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:50:10Z"
    - latency: 1.988958ms
      message: 'network-check-target-ip-10-0-128-108: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:49:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T13:37:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-33-to-network-check-target-ip-10-0-133-33
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-33.ec2.internal
      uid: 77b011f4-2888-47fe-a7c6-241a72395dd3
    resourceVersion: "33958"
    uid: 42427921-d960-4f02-9504-5ad4136cf0d1
  spec:
    sourcePod: network-check-source-8894fc9bd-7bc2w
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T13:44:10Z"
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.176686ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:58:10Z"
    - latency: 764.791µs
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:57:10Z"
    - latency: 1.033152ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:56:10Z"
    - latency: 1.000868ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:55:10Z"
    - latency: 1.189798ms
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:54:10Z"
    - latency: 935.479µs
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:53:10Z"
    - latency: 866.055µs
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:52:10Z"
    - latency: 968.128µs
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:51:10Z"
    - latency: 877.567µs
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:50:10Z"
    - latency: 817.867µs
      message: 'network-check-target-ip-10-0-133-33: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:49:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T13:37:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-33-to-network-check-target-ip-10-0-135-229
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-33.ec2.internal
      uid: 77b011f4-2888-47fe-a7c6-241a72395dd3
    resourceVersion: "33960"
    uid: ebfa6b9c-bc6b-4f43-b497-a0581bd8a6b8
  spec:
    sourcePod: network-check-source-8894fc9bd-7bc2w
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T13:44:10Z"
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.995539ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:58:10Z"
    - latency: 2.705225ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:57:10Z"
    - latency: 2.506471ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:56:10Z"
    - latency: 2.313088ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:55:10Z"
    - latency: 2.512324ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:54:10Z"
    - latency: 2.253162ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:53:10Z"
    - latency: 2.191393ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:52:10Z"
    - latency: 2.0932ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:51:10Z"
    - latency: 2.165337ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:50:10Z"
    - latency: 2.011599ms
      message: 'network-check-target-ip-10-0-135-229: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:49:10Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-23T13:37:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-33-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-33.ec2.internal
      uid: 77b011f4-2888-47fe-a7c6-241a72395dd3
    resourceVersion: "36351"
    uid: 5e537cf0-3775-4b03-83f0-4d6012147cd1
  spec:
    sourcePod: network-check-source-8894fc9bd-7bc2w
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-23T13:43:10Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 809.734µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:01:10Z"
    - latency: 1.837289ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:01:10Z"
    - latency: 894.041µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T14:00:10Z"
    - latency: 1.730021ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T14:00:10Z"
    - latency: 730.115µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:59:10Z"
    - latency: 2.023854ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T13:59:10Z"
    - latency: 926.453µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:58:10Z"
    - latency: 1.831951ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T13:58:10Z"
    - latency: 789.38µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-23T13:57:10Z"
    - latency: 1.792944ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-23T13:57:10Z"
kind: List
metadata:
  resourceVersion: ""