apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:48:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-56-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-56.ec2.internal
      uid: e001b90e-c57f-4a66-a3ec-a298999b83f5
    resourceVersion: "54419"
    uid: a46623fe-862c-40c4-ab6a-61caf9aa2a07
  spec:
    sourcePod: network-check-source-989f8b8dc-c8cx2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T13:55:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.331074ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:23:27Z"
    - latency: 853.481µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:22:27Z"
    - latency: 1.114763ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:21:27Z"
    - latency: 889.498µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:20:27Z"
    - latency: 969.173µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:19:27Z"
    - latency: 785.017µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:18:27Z"
    - latency: 1.236482ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:17:27Z"
    - latency: 1.39996ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:16:27Z"
    - latency: 4.898473ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:15:27Z"
    - latency: 973.748µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:14:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:48:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-56-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-56.ec2.internal
      uid: e001b90e-c57f-4a66-a3ec-a298999b83f5
    resourceVersion: "55427"
    uid: c16e3a37-1ba6-4cad-b2f3-4547e897ccf3
  spec:
    sourcePod: network-check-source-989f8b8dc-c8cx2
    targetEndpoint: a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T13:54:27Z"
      message: 'load-balancer-api-external: tcp connection to a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.496009ms
      message: 'load-balancer-api-external: tcp connection to a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:24:27Z"
    - latency: 10.124859ms
      message: 'load-balancer-api-external: resolved host name a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:24:27Z"
    - latency: 4.528456ms
      message: 'load-balancer-api-external: tcp connection to a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:23:27Z"
    - latency: 9.183061ms
      message: 'load-balancer-api-external: resolved host name a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:23:27Z"
    - latency: 4.738493ms
      message: 'load-balancer-api-external: tcp connection to a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:22:27Z"
    - latency: 8.473376ms
      message: 'load-balancer-api-external: resolved host name a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:22:27Z"
    - latency: 6.332896ms
      message: 'load-balancer-api-external: tcp connection to a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:21:27Z"
    - latency: 11.846174ms
      message: 'load-balancer-api-external: resolved host name a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:21:27Z"
    - latency: 5.418962ms
      message: 'load-balancer-api-external: tcp connection to a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:20:27Z"
    - latency: 7.124711ms
      message: 'load-balancer-api-external: resolved host name a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:20:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:48:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-56-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-56.ec2.internal
      uid: e001b90e-c57f-4a66-a3ec-a298999b83f5
    resourceVersion: "55426"
    uid: 87b01856-e84f-463a-9170-3a0b1a5a5334
  spec:
    sourcePod: network-check-source-989f8b8dc-c8cx2
    targetEndpoint: a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T13:54:27Z"
      message: 'load-balancer-api-internal: tcp connection to a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.162265ms
      message: 'load-balancer-api-internal: tcp connection to a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:24:27Z"
    - latency: 10.061286ms
      message: 'load-balancer-api-internal: resolved host name a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:24:27Z"
    - latency: 4.522604ms
      message: 'load-balancer-api-internal: tcp connection to a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:23:27Z"
    - latency: 9.107093ms
      message: 'load-balancer-api-internal: resolved host name a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:23:27Z"
    - latency: 6.698281ms
      message: 'load-balancer-api-internal: tcp connection to a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:22:27Z"
    - latency: 8.534364ms
      message: 'load-balancer-api-internal: resolved host name a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:22:27Z"
    - latency: 4.377044ms
      message: 'load-balancer-api-internal: tcp connection to a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:21:27Z"
    - latency: 11.873216ms
      message: 'load-balancer-api-internal: resolved host name a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:21:27Z"
    - latency: 5.110253ms
      message: 'load-balancer-api-internal: tcp connection to a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:20:27Z"
    - latency: 7.148309ms
      message: 'load-balancer-api-internal: resolved host name a45a4b220d83949a88595129aea61e3b-1135fd36ac3cb665.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:20:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:48:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-56-to-network-check-target-ip-10-0-134-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-56.ec2.internal
      uid: e001b90e-c57f-4a66-a3ec-a298999b83f5
    resourceVersion: "54418"
    uid: e49b4531-856b-4fd7-8cfd-790fd00ab011
  spec:
    sourcePod: network-check-source-989f8b8dc-c8cx2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T13:55:27Z"
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.452711ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:23:27Z"
    - latency: 2.234109ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:22:27Z"
    - latency: 2.523093ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:21:27Z"
    - latency: 2.225939ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:20:27Z"
    - latency: 2.414535ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:19:27Z"
    - latency: 2.557624ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:18:27Z"
    - latency: 2.762827ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:17:27Z"
    - latency: 2.705829ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:16:27Z"
    - latency: 2.993486ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:15:27Z"
    - latency: 1.993455ms
      message: 'network-check-target-ip-10-0-134-85: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:14:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:48:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-56-to-network-check-target-ip-10-0-142-56
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-56.ec2.internal
      uid: e001b90e-c57f-4a66-a3ec-a298999b83f5
    resourceVersion: "54416"
    uid: 41d1f5c7-2147-4b9e-a5e4-90e3f2f9769e
  spec:
    sourcePod: network-check-source-989f8b8dc-c8cx2
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T13:55:27Z"
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.507497ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:23:27Z"
    - latency: 899.54µs
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:22:27Z"
    - latency: 974.379µs
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:21:27Z"
    - latency: 936.114µs
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:20:27Z"
    - latency: 908.94µs
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:19:27Z"
    - latency: 1.144373ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:18:27Z"
    - latency: 1.390278ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:17:27Z"
    - latency: 1.222034ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:16:27Z"
    - latency: 1.022839ms
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:15:27Z"
    - latency: 684.174µs
      message: 'network-check-target-ip-10-0-142-56: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:14:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:48:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-56-to-network-check-target-ip-10-0-143-72
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-56.ec2.internal
      uid: e001b90e-c57f-4a66-a3ec-a298999b83f5
    resourceVersion: "54417"
    uid: 4393edd9-bc2a-4a55-98f5-bc0f5b970cde
  spec:
    sourcePod: network-check-source-989f8b8dc-c8cx2
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T13:55:27Z"
      message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.26342ms
      message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:23:27Z"
    - latency: 1.997398ms
      message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:22:27Z"
    - latency: 2.221675ms
      message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:21:27Z"
    - latency: 2.336792ms
      message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:20:27Z"
    - latency: 2.159418ms
      message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:19:27Z"
    - latency: 2.311183ms
      message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:18:27Z"
    - latency: 1.857043ms
      message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:17:27Z"
    - latency: 2.449627ms
      message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:16:27Z"
    - latency: 2.697091ms
      message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:15:27Z"
    - latency: 2.319266ms
      message: 'network-check-target-ip-10-0-143-72: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:14:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T13:48:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-56-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-56.ec2.internal
      uid: e001b90e-c57f-4a66-a3ec-a298999b83f5
    resourceVersion: "55425"
    uid: 4897cf64-5807-4c82-bcba-ba42d9725dbb
  spec:
    sourcePod: network-check-source-989f8b8dc-c8cx2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T13:54:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 858.255µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:24:27Z"
    - latency: 1.653998ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:24:27Z"
    - latency: 1.026888ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:23:27Z"
    - latency: 2.32159ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:23:27Z"
    - latency: 1.05934ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:22:27Z"
    - latency: 1.677711ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:22:27Z"
    - latency: 851.769µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:21:27Z"
    - latency: 1.868928ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:21:27Z"
    - latency: 750.891µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T14:20:27Z"
    - latency: 1.663294ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T14:20:27Z"
kind: List
metadata:
  resourceVersion: ""