apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-47-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-47.us-west-1.compute.internal
      uid: 7bca77ea-fb48-40dd-a627-65fa5ce84ebc
    resourceVersion: "169186"
    uid: bd1c0abb-f991-4ab6-8906-b25f5a062c03
  spec:
    sourcePod: network-check-source-6f78d59f99-76bkz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:29:44Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.212932ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:14:44Z"
    - latency: 1.043823ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:13:44Z"
    - latency: 1.103465ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:12:44Z"
    - latency: 951.228µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:11:44Z"
    - latency: 1.483706ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:10:44Z"
    - latency: 999.337µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:09:44Z"
    - latency: 1.421424ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:08:44Z"
    - latency: 1.822062ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:07:44Z"
    - latency: 765.919µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:06:44Z"
    - latency: 804.404µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:05:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-47-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-47.us-west-1.compute.internal
      uid: 7bca77ea-fb48-40dd-a627-65fa5ce84ebc
    resourceVersion: "171040"
    uid: 78d9c215-1c3a-40f6-bb51-9d081eff24c8
  spec:
    sourcePod: network-check-source-6f78d59f99-76bkz
    targetEndpoint: a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:28:44Z"
      message: 'load-balancer-api-external: tcp connection to a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.334028ms
      message: 'load-balancer-api-external: tcp connection to a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:16:44Z"
    - latency: 7.599191ms
      message: 'load-balancer-api-external: resolved host name a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:16:44Z"
    - latency: 52.919456ms
      message: 'load-balancer-api-external: tcp connection to a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:15:44Z"
    - latency: 7.154133ms
      message: 'load-balancer-api-external: resolved host name a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:15:44Z"
    - latency: 53.054759ms
      message: 'load-balancer-api-external: tcp connection to a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:14:44Z"
    - latency: 7.956747ms
      message: 'load-balancer-api-external: resolved host name a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:14:44Z"
    - latency: 53.282773ms
      message: 'load-balancer-api-external: tcp connection to a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:13:44Z"
    - latency: 7.701768ms
      message: 'load-balancer-api-external: resolved host name a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:13:44Z"
    - latency: 53.37193ms
      message: 'load-balancer-api-external: tcp connection to a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:12:44Z"
    - latency: 6.358953ms
      message: 'load-balancer-api-external: resolved host name a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:12:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-47-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-47.us-west-1.compute.internal
      uid: 7bca77ea-fb48-40dd-a627-65fa5ce84ebc
    resourceVersion: "171041"
    uid: 9b67ae07-10a5-4a40-8dc1-f69bdcec6769
  spec:
    sourcePod: network-check-source-6f78d59f99-76bkz
    targetEndpoint: a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:28:44Z"
      message: 'load-balancer-api-internal: tcp connection to a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 54.37264ms
      message: 'load-balancer-api-internal: tcp connection to a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:16:44Z"
    - latency: 7.669495ms
      message: 'load-balancer-api-internal: resolved host name a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:16:44Z"
    - latency: 53.123022ms
      message: 'load-balancer-api-internal: tcp connection to a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:15:44Z"
    - latency: 7.180588ms
      message: 'load-balancer-api-internal: resolved host name a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:15:44Z"
    - latency: 52.995591ms
      message: 'load-balancer-api-internal: tcp connection to a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:14:44Z"
    - latency: 7.98957ms
      message: 'load-balancer-api-internal: resolved host name a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:14:44Z"
    - latency: 53.296125ms
      message: 'load-balancer-api-internal: tcp connection to a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:13:44Z"
    - latency: 7.767702ms
      message: 'load-balancer-api-internal: resolved host name a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:13:44Z"
    - latency: 52.345076ms
      message: 'load-balancer-api-internal: tcp connection to a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:12:44Z"
    - latency: 6.37532ms
      message: 'load-balancer-api-internal: resolved host name a7971b018aa4c4793a97432a2228923c-30a6b095e3cfe1a3.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:12:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-47-to-network-check-target-ip-10-0-132-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-47.us-west-1.compute.internal
      uid: 7bca77ea-fb48-40dd-a627-65fa5ce84ebc
    resourceVersion: "169183"
    uid: bba03123-0440-4776-badf-60c0a9dec678
  spec:
    sourcePod: network-check-source-6f78d59f99-76bkz
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:29:44Z"
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.239311ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:14:44Z"
    - latency: 2.25667ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:13:44Z"
    - latency: 2.431418ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:12:44Z"
    - latency: 1.90086ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:11:44Z"
    - latency: 2.240037ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:10:44Z"
    - latency: 2.428711ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:09:44Z"
    - latency: 2.455933ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:08:44Z"
    - latency: 2.135352ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:07:44Z"
    - latency: 2.010652ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:06:44Z"
    - latency: 1.779449ms
      message: 'network-check-target-ip-10-0-132-99: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:05:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-47-to-network-check-target-ip-10-0-140-47
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-47.us-west-1.compute.internal
      uid: 7bca77ea-fb48-40dd-a627-65fa5ce84ebc
    resourceVersion: "169182"
    uid: 08afc0e2-3ca9-4b29-8dde-85ed2f817a2a
  spec:
    sourcePod: network-check-source-6f78d59f99-76bkz
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:29:44Z"
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.417485ms
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:14:44Z"
    - latency: 1.547052ms
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:13:44Z"
    - latency: 954.073µs
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:12:44Z"
    - latency: 928.967µs
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:11:44Z"
    - latency: 945.08µs
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:10:44Z"
    - latency: 957.384µs
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:09:44Z"
    - latency: 1.05383ms
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:08:44Z"
    - latency: 859.845µs
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:07:44Z"
    - latency: 746.034µs
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:06:44Z"
    - latency: 726.951µs
      message: 'network-check-target-ip-10-0-140-47: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:05:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-47-to-network-check-target-ip-10-0-142-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-47.us-west-1.compute.internal
      uid: 7bca77ea-fb48-40dd-a627-65fa5ce84ebc
    resourceVersion: "169184"
    uid: 7952c5cd-a4f9-446c-bf7a-4edef6cabfe7
  spec:
    sourcePod: network-check-source-6f78d59f99-76bkz
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:29:44Z"
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.0303ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:14:44Z"
    - latency: 2.336389ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:13:44Z"
    - latency: 2.096106ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:12:44Z"
    - latency: 1.947624ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:11:44Z"
    - latency: 2.0194ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:10:44Z"
    - latency: 1.919881ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:09:44Z"
    - latency: 2.397437ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:08:44Z"
    - latency: 1.933655ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:07:44Z"
    - latency: 1.973941ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:06:44Z"
    - latency: 11.833469ms
      message: 'network-check-target-ip-10-0-142-120: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:05:44Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T18:22:44Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-47-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-47.us-west-1.compute.internal
      uid: 7bca77ea-fb48-40dd-a627-65fa5ce84ebc
    resourceVersion: "171037"
    uid: 24c09137-3753-439d-a222-84376bc6eae9
  spec:
    sourcePod: network-check-source-6f78d59f99-76bkz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T18:28:44Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 844.018µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:16:44Z"
    - latency: 1.555538ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:16:44Z"
    - latency: 785.009µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:15:44Z"
    - latency: 1.465853ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:15:44Z"
    - latency: 910.464µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:14:44Z"
    - latency: 1.812441ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:14:44Z"
    - latency: 1.09987ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:13:44Z"
    - latency: 1.928523ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:13:44Z"
    - latency: 805.281µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:12:44Z"
    - latency: 1.695628ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:12:44Z"
kind: List
metadata:
  resourceVersion: ""