apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-105-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-105.us-west-2.compute.internal
      uid: 9868270f-1f5c-416d-a0c2-5b84217b565b
    resourceVersion: "113116"
    uid: 0b0cc242-7a89-4e6e-b8f6-21eef5d58a97
  spec:
    sourcePod: network-check-source-6f78d59f99-cz22k
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:37:06Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 985.041µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:33:06Z"
    - latency: 1.55293ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:32:06Z"
    - latency: 1.461314ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:31:06Z"
    - latency: 1.315848ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:30:06Z"
    - latency: 1.362048ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:29:06Z"
    - latency: 1.755231ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:28:06Z"
    - latency: 1.626101ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:06Z"
    - latency: 1.792072ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:06Z"
    - latency: 1.594273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:06Z"
    - latency: 978.495µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-105-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-105.us-west-2.compute.internal
      uid: 9868270f-1f5c-416d-a0c2-5b84217b565b
    resourceVersion: "107613"
    uid: ccfbcfe1-56ed-41a5-b3f9-a57c91e79f41
  spec:
    sourcePod: network-check-source-6f78d59f99-cz22k
    targetEndpoint: a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:36:06Z"
      message: 'load-balancer-api-external: tcp connection to a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 51.651086ms
      message: 'load-balancer-api-external: tcp connection to a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:30:06Z"
    - latency: 7.068439ms
      message: 'load-balancer-api-external: resolved host name a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:30:06Z"
    - latency: 57.692758ms
      message: 'load-balancer-api-external: tcp connection to a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:29:06Z"
    - latency: 6.882425ms
      message: 'load-balancer-api-external: resolved host name a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:29:06Z"
    - latency: 50.725012ms
      message: 'load-balancer-api-external: tcp connection to a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:28:06Z"
    - latency: 7.703741ms
      message: 'load-balancer-api-external: resolved host name a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:28:06Z"
    - latency: 55.099297ms
      message: 'load-balancer-api-external: tcp connection to a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:06Z"
    - latency: 8.127857ms
      message: 'load-balancer-api-external: resolved host name a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:27:06Z"
    - latency: 55.67561ms
      message: 'load-balancer-api-external: tcp connection to a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:06Z"
    - latency: 7.363321ms
      message: 'load-balancer-api-external: resolved host name a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:26:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-105-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-105.us-west-2.compute.internal
      uid: 9868270f-1f5c-416d-a0c2-5b84217b565b
    resourceVersion: "107615"
    uid: 7938a585-379b-414d-a90e-760dc93daf90
  spec:
    sourcePod: network-check-source-6f78d59f99-cz22k
    targetEndpoint: a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:36:06Z"
      message: 'load-balancer-api-internal: tcp connection to a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 59.568505ms
      message: 'load-balancer-api-internal: tcp connection to a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:30:06Z"
    - latency: 7.10397ms
      message: 'load-balancer-api-internal: resolved host name a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:30:06Z"
    - latency: 55.206662ms
      message: 'load-balancer-api-internal: tcp connection to a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:29:06Z"
    - latency: 6.921963ms
      message: 'load-balancer-api-internal: resolved host name a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:29:06Z"
    - latency: 55.846084ms
      message: 'load-balancer-api-internal: tcp connection to a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:28:06Z"
    - latency: 7.662696ms
      message: 'load-balancer-api-internal: resolved host name a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:28:06Z"
    - latency: 51.483335ms
      message: 'load-balancer-api-internal: tcp connection to a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:06Z"
    - latency: 8.162079ms
      message: 'load-balancer-api-internal: resolved host name a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:27:06Z"
    - latency: 54.930003ms
      message: 'load-balancer-api-internal: tcp connection to a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:06Z"
    - latency: 7.394333ms
      message: 'load-balancer-api-internal: resolved host name a5bf11d8d49064afc9ef2bd5f2126127-faee8f219fa21b80.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:26:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-105-to-network-check-target-ip-10-0-129-8
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-105.us-west-2.compute.internal
      uid: 9868270f-1f5c-416d-a0c2-5b84217b565b
    resourceVersion: "113111"
    uid: 35ac4499-01bf-45d4-9764-d8acf3cfc6a1
  spec:
    sourcePod: network-check-source-6f78d59f99-cz22k
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:37:06Z"
      message: 'network-check-target-ip-10-0-129-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.838083ms
      message: 'network-check-target-ip-10-0-129-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:33:06Z"
    - latency: 2.409358ms
      message: 'network-check-target-ip-10-0-129-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:32:06Z"
    - latency: 2.415946ms
      message: 'network-check-target-ip-10-0-129-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:31:06Z"
    - latency: 2.283254ms
      message: 'network-check-target-ip-10-0-129-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:30:06Z"
    - latency: 2.487566ms
      message: 'network-check-target-ip-10-0-129-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:29:06Z"
    - latency: 2.561512ms
      message: 'network-check-target-ip-10-0-129-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:28:06Z"
    - latency: 2.422408ms
      message: 'network-check-target-ip-10-0-129-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:06Z"
    - latency: 2.39056ms
      message: 'network-check-target-ip-10-0-129-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:06Z"
    - latency: 2.364173ms
      message: 'network-check-target-ip-10-0-129-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:06Z"
    - latency: 2.73489ms
      message: 'network-check-target-ip-10-0-129-8: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-105-to-network-check-target-ip-10-0-132-173
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-105.us-west-2.compute.internal
      uid: 9868270f-1f5c-416d-a0c2-5b84217b565b
    resourceVersion: "113112"
    uid: dfe41ef5-25f2-4c11-86e4-c2f5b400411e
  spec:
    sourcePod: network-check-source-6f78d59f99-cz22k
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:37:06Z"
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.240751ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:33:06Z"
    - latency: 2.666972ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:32:06Z"
    - latency: 2.237896ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:31:06Z"
    - latency: 2.445753ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:30:06Z"
    - latency: 2.592329ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:29:06Z"
    - latency: 2.584289ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:28:06Z"
    - latency: 2.371802ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:06Z"
    - latency: 2.658045ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:06Z"
    - latency: 3.291298ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:06Z"
    - latency: 2.734058ms
      message: 'network-check-target-ip-10-0-132-173: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-105-to-network-check-target-ip-10-0-143-105
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-105.us-west-2.compute.internal
      uid: 9868270f-1f5c-416d-a0c2-5b84217b565b
    resourceVersion: "113110"
    uid: 7ee3daba-bbcb-42af-9b47-41e7f7911646
  spec:
    sourcePod: network-check-source-6f78d59f99-cz22k
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:37:06Z"
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 969.483µs
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:33:06Z"
    - latency: 1.772532ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:32:06Z"
    - latency: 1.146733ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:31:06Z"
    - latency: 1.356465ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:30:06Z"
    - latency: 1.600601ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:29:06Z"
    - latency: 1.133575ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:28:06Z"
    - latency: 1.554133ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:06Z"
    - latency: 2.159727ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:06Z"
    - latency: 1.98558ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:25:06Z"
    - latency: 1.123203ms
      message: 'network-check-target-ip-10-0-143-105: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:24:06Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T00:30:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-143-105-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-143-105.us-west-2.compute.internal
      uid: 9868270f-1f5c-416d-a0c2-5b84217b565b
    resourceVersion: "107608"
    uid: 1bbdfeef-db4b-4bed-9e3d-00d59b9621e4
  spec:
    sourcePod: network-check-source-6f78d59f99-cz22k
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T00:36:06Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 997.789µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:30:06Z"
    - latency: 2.385035ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:30:06Z"
    - latency: 1.621292ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:29:06Z"
    - latency: 1.992269ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:29:06Z"
    - latency: 1.125204ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:28:06Z"
    - latency: 2.43794ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:28:06Z"
    - latency: 1.278517ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:27:06Z"
    - latency: 2.364613ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:27:06Z"
    - latency: 1.431256ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T01:26:06Z"
    - latency: 2.360128ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T01:26:06Z"
kind: List
metadata:
  resourceVersion: ""