apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:38:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-166-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-166.ec2.internal
      uid: 50360495-3267-4fc7-b39c-1a966738dace
    resourceVersion: "23375"
    uid: ee7993e7-e047-47f3-9018-e16379013eb7
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qkf2
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:45:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.050038ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:52:16Z"
    - latency: 1.191073ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:51:16Z"
    - latency: 929.663µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:50:16Z"
    - latency: 1.114952ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:49:16Z"
    - latency: 1.234822ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:48:16Z"
    - latency: 965.654µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:47:16Z"
    - latency: 1.18885ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:46:16Z"
    - latency: 1.049318ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:45:16Z"
    - latency: 862.217µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:44:16Z"
    - latency: 910.084µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:43:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:38:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-166-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-166.ec2.internal
      uid: 50360495-3267-4fc7-b39c-1a966738dace
    resourceVersion: "22229"
    uid: 21bd7c99-1a0e-4c27-a28d-6238a0e1a17a
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qkf2
    targetEndpoint: a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:44:16Z"
      message: 'load-balancer-api-external: tcp connection to a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.917552ms
      message: 'load-balancer-api-external: tcp connection to a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:50:16Z"
    - latency: 8.07452ms
      message: 'load-balancer-api-external: resolved host name a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:50:16Z"
    - latency: 5.8019ms
      message: 'load-balancer-api-external: tcp connection to a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:49:16Z"
    - latency: 9.36692ms
      message: 'load-balancer-api-external: resolved host name a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:49:16Z"
    - latency: 5.5614ms
      message: 'load-balancer-api-external: tcp connection to a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:48:16Z"
    - latency: 9.423879ms
      message: 'load-balancer-api-external: resolved host name a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:48:16Z"
    - latency: 5.705171ms
      message: 'load-balancer-api-external: tcp connection to a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:47:16Z"
    - latency: 9.100011ms
      message: 'load-balancer-api-external: resolved host name a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:47:16Z"
    - latency: 3.899425ms
      message: 'load-balancer-api-external: tcp connection to a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:46:16Z"
    - latency: 8.071349ms
      message: 'load-balancer-api-external: resolved host name a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:46:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:38:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-166-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-166.ec2.internal
      uid: 50360495-3267-4fc7-b39c-1a966738dace
    resourceVersion: "22227"
    uid: 4cf06149-de4e-4d42-87a6-c7acfad6ed76
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qkf2
    targetEndpoint: a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:44:16Z"
      message: 'load-balancer-api-internal: tcp connection to a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.942821ms
      message: 'load-balancer-api-internal: tcp connection to a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:50:16Z"
    - latency: 8.180431ms
      message: 'load-balancer-api-internal: resolved host name a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:50:16Z"
    - latency: 6.125333ms
      message: 'load-balancer-api-internal: tcp connection to a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:49:16Z"
    - latency: 9.324795ms
      message: 'load-balancer-api-internal: resolved host name a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:49:16Z"
    - latency: 5.570015ms
      message: 'load-balancer-api-internal: tcp connection to a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:48:16Z"
    - latency: 9.507236ms
      message: 'load-balancer-api-internal: resolved host name a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:48:16Z"
    - latency: 5.663754ms
      message: 'load-balancer-api-internal: tcp connection to a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:47:16Z"
    - latency: 9.243441ms
      message: 'load-balancer-api-internal: resolved host name a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:47:16Z"
    - latency: 4.598421ms
      message: 'load-balancer-api-internal: tcp connection to a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:46:16Z"
    - latency: 8.017733ms
      message: 'load-balancer-api-internal: resolved host name a07c9ce0474664f369a5a6848ee8ec66-759304cbbb780ff2.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:46:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:38:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-166-to-network-check-target-ip-10-0-134-93
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-166.ec2.internal
      uid: 50360495-3267-4fc7-b39c-1a966738dace
    resourceVersion: "23373"
    uid: 8d262d2e-6105-48e1-b360-7013c0d65d88
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qkf2
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:45:16Z"
      message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.875456ms
      message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:52:16Z"
    - latency: 1.645097ms
      message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:51:16Z"
    - latency: 1.704282ms
      message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:50:16Z"
    - latency: 1.991685ms
      message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:49:16Z"
    - latency: 1.914424ms
      message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:48:16Z"
    - latency: 1.81695ms
      message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:47:16Z"
    - latency: 1.917461ms
      message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:46:16Z"
    - latency: 1.830028ms
      message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:45:16Z"
    - latency: 1.733149ms
      message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:44:16Z"
    - latency: 1.926861ms
      message: 'network-check-target-ip-10-0-134-93: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:43:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:38:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-166-to-network-check-target-ip-10-0-137-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-166.ec2.internal
      uid: 50360495-3267-4fc7-b39c-1a966738dace
    resourceVersion: "23372"
    uid: 74dd464f-de04-4dbd-87ab-581d3fc080aa
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qkf2
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:45:16Z"
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.898µs
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:52:16Z"
    - latency: 934.88µs
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:51:16Z"
    - latency: 810.001µs
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:50:16Z"
    - latency: 1.311584ms
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:49:16Z"
    - latency: 756.789µs
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:48:16Z"
    - latency: 1.536179ms
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:47:16Z"
    - latency: 1.351195ms
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:46:16Z"
    - latency: 1.253106ms
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:45:16Z"
    - latency: 1.365833ms
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:44:16Z"
    - latency: 815.647µs
      message: 'network-check-target-ip-10-0-137-166: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:43:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:38:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-166-to-network-check-target-ip-10-0-143-192
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-166.ec2.internal
      uid: 50360495-3267-4fc7-b39c-1a966738dace
    resourceVersion: "23374"
    uid: 2d501896-bfec-487c-ac1c-2fad97a4c778
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qkf2
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:45:16Z"
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.315359ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:52:16Z"
    - latency: 2.353733ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:51:16Z"
    - latency: 2.468898ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:50:16Z"
    - latency: 2.367785ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:49:16Z"
    - latency: 2.3045ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:48:16Z"
    - latency: 2.283283ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:47:16Z"
    - latency: 2.256247ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:46:16Z"
    - latency: 2.378406ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:45:16Z"
    - latency: 2.375325ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:44:16Z"
    - latency: 2.257429ms
      message: 'network-check-target-ip-10-0-143-192: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:43:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-28T12:38:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-137-166-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-137-166.ec2.internal
      uid: 50360495-3267-4fc7-b39c-1a966738dace
    resourceVersion: "22226"
    uid: b775c36c-ee65-4dde-8211-70bbde5c8a77
  spec:
    sourcePod: network-check-source-7d88cb55d8-4qkf2
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-28T12:44:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.016515ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:50:16Z"
    - latency: 1.612234ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:50:16Z"
    - latency: 1.018709ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:49:16Z"
    - latency: 2.470238ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:49:16Z"
    - latency: 882.59µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:48:16Z"
    - latency: 1.874373ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:48:16Z"
    - latency: 976.838µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:47:16Z"
    - latency: 2.111009ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:47:16Z"
    - latency: 1.050831ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-28T12:46:16Z"
    - latency: 1.773283ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-28T12:46:16Z"
kind: List
metadata:
  resourceVersion: ""