apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T14:38:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 275e5b53-7de2-400e-a3a4-c585999e53da
    resourceVersion: "62180"
    uid: 837b1351-1b59-4aa0-9778-f606a5ac62f6
  spec:
    sourcePod: network-check-source-869dcfcdcd-4rjgr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:45:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.99975ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:20:05Z"
    - latency: 1.497973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:19:05Z"
    - latency: 1.330661ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:18:05Z"
    - latency: 991.09µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:17:05Z"
    - latency: 1.571407ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:16:05Z"
    - latency: 1.438003ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:15:05Z"
    - latency: 1.030448ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:14:05Z"
    - latency: 1.018213ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:13:05Z"
    - latency: 1.302796ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:12:05Z"
    - latency: 2.332649ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:11:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T14:38:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 275e5b53-7de2-400e-a3a4-c585999e53da
    resourceVersion: "62182"
    uid: d9c13727-390b-4cbf-a287-c99bc963563e
  spec:
    sourcePod: network-check-source-869dcfcdcd-4rjgr
    targetEndpoint: a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:44:05Z"
      message: 'load-balancer-api-external: tcp connection to a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.089461ms
      message: 'load-balancer-api-external: tcp connection to a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:20:05Z"
    - latency: 9.761984ms
      message: 'load-balancer-api-external: resolved host name a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:20:05Z"
    - latency: 4.830375ms
      message: 'load-balancer-api-external: tcp connection to a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:19:05Z"
    - latency: 9.434089ms
      message: 'load-balancer-api-external: resolved host name a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:19:05Z"
    - latency: 3.565246ms
      message: 'load-balancer-api-external: tcp connection to a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:18:05Z"
    - latency: 8.927376ms
      message: 'load-balancer-api-external: resolved host name a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:18:05Z"
    - latency: 3.978004ms
      message: 'load-balancer-api-external: tcp connection to a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:17:05Z"
    - latency: 12.455539ms
      message: 'load-balancer-api-external: resolved host name a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:17:05Z"
    - latency: 5.302664ms
      message: 'load-balancer-api-external: tcp connection to a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:16:05Z"
    - latency: 10.023576ms
      message: 'load-balancer-api-external: resolved host name a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:16:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T14:38:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 275e5b53-7de2-400e-a3a4-c585999e53da
    resourceVersion: "62183"
    uid: 4f3f9d3d-bb9a-486b-83fd-9ce40e09ab1f
  spec:
    sourcePod: network-check-source-869dcfcdcd-4rjgr
    targetEndpoint: a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:44:05Z"
      message: 'load-balancer-api-internal: tcp connection to a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.321527ms
      message: 'load-balancer-api-internal: tcp connection to a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:20:05Z"
    - latency: 9.731066ms
      message: 'load-balancer-api-internal: resolved host name a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:20:05Z"
    - latency: 3.049214ms
      message: 'load-balancer-api-internal: tcp connection to a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:19:05Z"
    - latency: 9.500717ms
      message: 'load-balancer-api-internal: resolved host name a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:19:05Z"
    - latency: 4.06956ms
      message: 'load-balancer-api-internal: tcp connection to a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:18:05Z"
    - latency: 8.913198ms
      message: 'load-balancer-api-internal: resolved host name a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:18:05Z"
    - latency: 4.458682ms
      message: 'load-balancer-api-internal: tcp connection to a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:17:05Z"
    - latency: 12.426558ms
      message: 'load-balancer-api-internal: resolved host name a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:17:05Z"
    - latency: 3.799196ms
      message: 'load-balancer-api-internal: tcp connection to a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:16:05Z"
    - latency: 10.095526ms
      message: 'load-balancer-api-internal: resolved host name a058d005d278144e4888c0f2b6a86b67-b51391bb34f85a13.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:16:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T14:38:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-139-83
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 275e5b53-7de2-400e-a3a4-c585999e53da
    resourceVersion: "62176"
    uid: a2f1336f-d7f8-4e12-ad43-420ab568af02
  spec:
    sourcePod: network-check-source-869dcfcdcd-4rjgr
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:45:05Z"
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.267573ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:20:05Z"
    - latency: 2.322476ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:19:05Z"
    - latency: 2.236341ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:18:05Z"
    - latency: 2.154356ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:17:05Z"
    - latency: 2.38293ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:16:05Z"
    - latency: 3.356686ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:15:05Z"
    - latency: 2.490248ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:14:05Z"
    - latency: 2.655572ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:13:05Z"
    - latency: 2.370028ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:12:05Z"
    - latency: 1.882751ms
      message: 'network-check-target-ip-10-0-139-83: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:11:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T14:38:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-140-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 275e5b53-7de2-400e-a3a4-c585999e53da
    resourceVersion: "62178"
    uid: 9d31d245-4204-4af5-871d-edeadd2651dd
  spec:
    sourcePod: network-check-source-869dcfcdcd-4rjgr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:45:05Z"
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.048529ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:20:05Z"
    - latency: 1.439967ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:19:05Z"
    - latency: 1.024958ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:18:05Z"
    - latency: 901.945µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:17:05Z"
    - latency: 968.703µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:16:05Z"
    - latency: 1.421306ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:15:05Z"
    - latency: 1.793019ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:14:05Z"
    - latency: 911.37µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:13:05Z"
    - latency: 954.192µs
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:12:05Z"
    - latency: 1.453269ms
      message: 'network-check-target-ip-10-0-140-61: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:11:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T14:38:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-ip-10-0-141-12
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 275e5b53-7de2-400e-a3a4-c585999e53da
    resourceVersion: "62177"
    uid: e79a03c2-9c65-4537-aa73-477c71e50ac1
  spec:
    sourcePod: network-check-source-869dcfcdcd-4rjgr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:45:05Z"
      message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.446503ms
      message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:20:05Z"
    - latency: 2.61611ms
      message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:19:05Z"
    - latency: 2.491509ms
      message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:18:05Z"
    - latency: 2.145669ms
      message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:17:05Z"
    - latency: 2.330058ms
      message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:16:05Z"
    - latency: 2.962427ms
      message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:15:05Z"
    - latency: 2.644832ms
      message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:14:05Z"
    - latency: 2.626302ms
      message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:13:05Z"
    - latency: 2.258304ms
      message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:12:05Z"
    - latency: 2.700845ms
      message: 'network-check-target-ip-10-0-141-12: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:11:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-15T14:38:04Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-61.ec2.internal
      uid: 275e5b53-7de2-400e-a3a4-c585999e53da
    resourceVersion: "62179"
    uid: e7823e9d-8043-4b7f-9cf3-ff22c67d01c1
  spec:
    sourcePod: network-check-source-869dcfcdcd-4rjgr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-15T14:44:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 883.647µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:20:05Z"
    - latency: 2.873534ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:20:05Z"
    - latency: 962.551µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:19:05Z"
    - latency: 1.686177ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:19:05Z"
    - latency: 994.218µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:18:05Z"
    - latency: 1.928388ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:18:05Z"
    - latency: 1.054956ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:17:05Z"
    - latency: 2.0974ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:17:05Z"
    - latency: 1.201552ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-15T15:16:05Z"
    - latency: 2.006759ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-15T15:16:05Z"
kind: List
metadata:
  resourceVersion: ""