apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T14:57:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-143-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-143.ec2.internal
      uid: 456661d4-0d77-4fc1-bc1a-970d91f835ac
    resourceVersion: "175602"
    uid: e33f07b9-9cce-49f0-98e8-62a8872f499e
  spec:
    sourcePod: network-check-source-6f78d59f99-hv272
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T15:04:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.339773ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:14:06Z"
    - latency: 1.270171ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:13:06Z"
    - latency: 1.400879ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:12:06Z"
    - latency: 1.124471ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:11:06Z"
    - latency: 1.116806ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:10:06Z"
    - latency: 1.1311ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:09:06Z"
    - latency: 1.060668ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:08:06Z"
    - latency: 1.246893ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:07:06Z"
    - latency: 1.288504ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:06:06Z"
    - latency: 1.34965ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:05:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T14:57:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-143-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-143.ec2.internal
      uid: 456661d4-0d77-4fc1-bc1a-970d91f835ac
    resourceVersion: "176191"
    uid: b7118d74-a07c-42b3-8987-7258be2d2408
  spec:
    sourcePod: network-check-source-6f78d59f99-hv272
    targetEndpoint: ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T15:03:06Z"
      message: 'load-balancer-api-external: tcp connection to ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 17.411284ms
      message: 'load-balancer-api-external: tcp connection to ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:15:06Z"
    - latency: 6.873774ms
      message: 'load-balancer-api-external: resolved host name ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:15:06Z"
    - latency: 15.335861ms
      message: 'load-balancer-api-external: tcp connection to ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:14:06Z"
    - latency: 6.582628ms
      message: 'load-balancer-api-external: resolved host name ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:14:06Z"
    - latency: 18.284237ms
      message: 'load-balancer-api-external: tcp connection to ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:13:06Z"
    - latency: 6.763564ms
      message: 'load-balancer-api-external: resolved host name ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:13:06Z"
    - latency: 16.596158ms
      message: 'load-balancer-api-external: tcp connection to ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:12:06Z"
    - latency: 6.798689ms
      message: 'load-balancer-api-external: resolved host name ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:12:06Z"
    - latency: 17.012621ms
      message: 'load-balancer-api-external: tcp connection to ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:11:06Z"
    - latency: 5.573038ms
      message: 'load-balancer-api-external: resolved host name ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:11:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T14:57:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-143-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-143.ec2.internal
      uid: 456661d4-0d77-4fc1-bc1a-970d91f835ac
    resourceVersion: "176190"
    uid: 595fc5f0-09f5-4928-9b39-dab5b88dc54e
  spec:
    sourcePod: network-check-source-6f78d59f99-hv272
    targetEndpoint: ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T15:03:06Z"
      message: 'load-balancer-api-internal: tcp connection to ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.753688ms
      message: 'load-balancer-api-internal: tcp connection to ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:15:06Z"
    - latency: 6.893645ms
      message: 'load-balancer-api-internal: resolved host name ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:15:06Z"
    - latency: 15.457656ms
      message: 'load-balancer-api-internal: tcp connection to ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:14:06Z"
    - latency: 6.623737ms
      message: 'load-balancer-api-internal: resolved host name ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:14:06Z"
    - latency: 18.007832ms
      message: 'load-balancer-api-internal: tcp connection to ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:13:06Z"
    - latency: 6.740562ms
      message: 'load-balancer-api-internal: resolved host name ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:13:06Z"
    - latency: 16.93735ms
      message: 'load-balancer-api-internal: tcp connection to ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:12:06Z"
    - latency: 6.720494ms
      message: 'load-balancer-api-internal: resolved host name ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:12:06Z"
    - latency: 17.9025ms
      message: 'load-balancer-api-internal: tcp connection to ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:11:06Z"
    - latency: 5.512722ms
      message: 'load-balancer-api-internal: resolved host name ae1023638ca6449a48b8a351100d96a3-be41b57f0e73983d.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:11:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T14:57:18Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-143-to-network-check-target-ip-10-0-129-45
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-143.ec2.internal
      uid: 456661d4-0d77-4fc1-bc1a-970d91f835ac
    resourceVersion: "175718"
    uid: db74b24f-2dbf-4273-88bf-fe547d9e2df7
  spec:
    sourcePod: network-check-source-6f78d59f99-hv272
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T15:04:18Z"
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.222555ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:14:18Z"
    - latency: 6.756427ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:13:18Z"
    - latency: 2.485571ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:12:18Z"
    - latency: 2.323672ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:11:18Z"
    - latency: 2.55693ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:10:18Z"
    - latency: 3.190939ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:09:18Z"
    - latency: 2.267375ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:08:18Z"
    - latency: 2.501071ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:07:18Z"
    - latency: 2.312318ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:06:18Z"
    - latency: 2.15162ms
      message: 'network-check-target-ip-10-0-129-45: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:05:18Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T14:57:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-143-to-network-check-target-ip-10-0-133-143
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-143.ec2.internal
      uid: 456661d4-0d77-4fc1-bc1a-970d91f835ac
    resourceVersion: "175601"
    uid: 46e5f35d-cceb-4e3c-b849-293752dab084
  spec:
    sourcePod: network-check-source-6f78d59f99-hv272
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T15:04:06Z"
      message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.630088ms
      message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:14:06Z"
    - latency: 1.220459ms
      message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:13:06Z"
    - latency: 1.542485ms
      message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:12:06Z"
    - latency: 1.489073ms
      message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:11:06Z"
    - latency: 1.359399ms
      message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:10:06Z"
    - latency: 1.429958ms
      message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:09:06Z"
    - latency: 1.136864ms
      message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:08:06Z"
    - latency: 1.588538ms
      message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:07:06Z"
    - latency: 1.23501ms
      message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:06:06Z"
    - latency: 1.614893ms
      message: 'network-check-target-ip-10-0-133-143: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:05:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T14:57:12Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-143-to-network-check-target-ip-10-0-135-138
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-143.ec2.internal
      uid: 456661d4-0d77-4fc1-bc1a-970d91f835ac
    resourceVersion: "175654"
    uid: ce6ad87e-cef3-4b68-b9d7-dc56294ce71e
  spec:
    sourcePod: network-check-source-6f78d59f99-hv272
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T15:04:12Z"
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.028168ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:14:12Z"
    - latency: 2.142557ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:13:12Z"
    - latency: 1.16113ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:12:12Z"
    - latency: 758.519µs
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:11:12Z"
    - latency: 2.495548ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:10:12Z"
    - latency: 2.538619ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:09:12Z"
    - latency: 1.035988ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:08:12Z"
    - latency: 2.206788ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:07:12Z"
    - latency: 2.201998ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:06:12Z"
    - latency: 2.115641ms
      message: 'network-check-target-ip-10-0-135-138: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:05:12Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T14:57:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-143-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-143.ec2.internal
      uid: 456661d4-0d77-4fc1-bc1a-970d91f835ac
    resourceVersion: "176189"
    uid: 9754fb1b-bfee-4394-ab85-2d839224dbb8
  spec:
    sourcePod: network-check-source-6f78d59f99-hv272
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T15:03:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.834305ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:15:06Z"
    - latency: 1.961193ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:15:06Z"
    - latency: 2.466197ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:14:06Z"
    - latency: 1.884288ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:14:06Z"
    - latency: 744.038µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:13:06Z"
    - latency: 2.009639ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:13:06Z"
    - latency: 2.138072ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:12:06Z"
    - latency: 1.951844ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:12:06Z"
    - latency: 2.466889ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T16:11:06Z"
    - latency: 1.656886ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T16:11:06Z"
kind: List
metadata:
  resourceVersion: ""