apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T19:19:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-104-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-104.us-west-2.compute.internal
      uid: 1f3956b8-1ccf-4482-916d-03ab60194916
    resourceVersion: "112841"
    uid: f858d7ac-76ec-471d-aaac-f34b4fcd5afe
  spec:
    sourcePod: network-check-source-6f78d59f99-zkvsg
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T19:26:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.540514ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:36:07Z"
    - latency: 1.238752ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:35:07Z"
    - latency: 1.345822ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:34:07Z"
    - latency: 1.193873ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:33:07Z"
    - latency: 1.255779ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:32:07Z"
    - latency: 1.632409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:31:07Z"
    - latency: 1.330242ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:30:07Z"
    - latency: 2.488759ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:29:07Z"
    - latency: 1.803655ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:28:07Z"
    - latency: 1.181761ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:27:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T19:19:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-104-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-104.us-west-2.compute.internal
      uid: 1f3956b8-1ccf-4482-916d-03ab60194916
    resourceVersion: "113347"
    uid: 2f400aa0-edf2-4bff-b53e-883907494979
  spec:
    sourcePod: network-check-source-6f78d59f99-zkvsg
    targetEndpoint: aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T19:25:07Z"
      message: 'load-balancer-api-external: tcp connection to aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 50.722802ms
      message: 'load-balancer-api-external: tcp connection to aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:37:07Z"
    - latency: 7.13531ms
      message: 'load-balancer-api-external: resolved host name aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:37:07Z"
    - latency: 55.076186ms
      message: 'load-balancer-api-external: tcp connection to aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:36:07Z"
    - latency: 6.765572ms
      message: 'load-balancer-api-external: resolved host name aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:36:07Z"
    - latency: 53.296202ms
      message: 'load-balancer-api-external: tcp connection to aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:35:07Z"
    - latency: 6.769534ms
      message: 'load-balancer-api-external: resolved host name aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:35:07Z"
    - latency: 49.782193ms
      message: 'load-balancer-api-external: tcp connection to aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:34:07Z"
    - latency: 6.550089ms
      message: 'load-balancer-api-external: resolved host name aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:34:07Z"
    - latency: 55.078673ms
      message: 'load-balancer-api-external: tcp connection to aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:33:07Z"
    - latency: 8.302569ms
      message: 'load-balancer-api-external: resolved host name aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:33:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T19:19:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-104-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-104.us-west-2.compute.internal
      uid: 1f3956b8-1ccf-4482-916d-03ab60194916
    resourceVersion: "113346"
    uid: bfe0e919-4be1-47bb-9947-fd34667be5d8
  spec:
    sourcePod: network-check-source-6f78d59f99-zkvsg
    targetEndpoint: aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T19:25:07Z"
      message: 'load-balancer-api-internal: tcp connection to aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 50.511436ms
      message: 'load-balancer-api-internal: tcp connection to aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:37:07Z"
    - latency: 7.218941ms
      message: 'load-balancer-api-internal: resolved host name aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:37:07Z"
    - latency: 51.807636ms
      message: 'load-balancer-api-internal: tcp connection to aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:36:07Z"
    - latency: 6.667459ms
      message: 'load-balancer-api-internal: resolved host name aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:36:07Z"
    - latency: 53.930819ms
      message: 'load-balancer-api-internal: tcp connection to aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:35:07Z"
    - latency: 6.849443ms
      message: 'load-balancer-api-internal: resolved host name aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:35:07Z"
    - latency: 49.80046ms
      message: 'load-balancer-api-internal: tcp connection to aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:34:07Z"
    - latency: 6.485781ms
      message: 'load-balancer-api-internal: resolved host name aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:34:07Z"
    - latency: 50.676362ms
      message: 'load-balancer-api-internal: tcp connection to aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:33:07Z"
    - latency: 8.156762ms
      message: 'load-balancer-api-internal: resolved host name aa8143aa486024233b53a2014e030d47-5fe5f50e5295cc6b.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:33:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T19:19:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-104-to-network-check-target-ip-10-0-128-104
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-104.us-west-2.compute.internal
      uid: 1f3956b8-1ccf-4482-916d-03ab60194916
    resourceVersion: "112836"
    uid: 9c49951b-9ab3-4d4e-a1fa-960db30f167a
  spec:
    sourcePod: network-check-source-6f78d59f99-zkvsg
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T19:26:07Z"
      message: 'network-check-target-ip-10-0-128-104: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.603208ms
      message: 'network-check-target-ip-10-0-128-104: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:36:07Z"
    - latency: 858.111µs
      message: 'network-check-target-ip-10-0-128-104: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:35:07Z"
    - latency: 1.205324ms
      message: 'network-check-target-ip-10-0-128-104: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:34:07Z"
    - latency: 979.228µs
      message: 'network-check-target-ip-10-0-128-104: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:33:07Z"
    - latency: 970.7µs
      message: 'network-check-target-ip-10-0-128-104: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:32:07Z"
    - latency: 1.911066ms
      message: 'network-check-target-ip-10-0-128-104: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:31:07Z"
    - latency: 1.577497ms
      message: 'network-check-target-ip-10-0-128-104: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:30:07Z"
    - latency: 3.130963ms
      message: 'network-check-target-ip-10-0-128-104: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:29:07Z"
    - latency: 1.007919ms
      message: 'network-check-target-ip-10-0-128-104: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:28:07Z"
    - latency: 908.491µs
      message: 'network-check-target-ip-10-0-128-104: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:27:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T19:19:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-104-to-network-check-target-ip-10-0-128-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-104.us-west-2.compute.internal
      uid: 1f3956b8-1ccf-4482-916d-03ab60194916
    resourceVersion: "112839"
    uid: 37e76e28-3a1f-4682-a3ff-575d4758bb02
  spec:
    sourcePod: network-check-source-6f78d59f99-zkvsg
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T19:26:07Z"
      message: 'network-check-target-ip-10-0-128-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.232926ms
      message: 'network-check-target-ip-10-0-128-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:36:07Z"
    - latency: 2.139534ms
      message: 'network-check-target-ip-10-0-128-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:35:07Z"
    - latency: 2.309446ms
      message: 'network-check-target-ip-10-0-128-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:34:07Z"
    - latency: 1.93354ms
      message: 'network-check-target-ip-10-0-128-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:33:07Z"
    - latency: 1.990306ms
      message: 'network-check-target-ip-10-0-128-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:32:07Z"
    - latency: 1.954118ms
      message: 'network-check-target-ip-10-0-128-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:31:07Z"
    - latency: 2.225485ms
      message: 'network-check-target-ip-10-0-128-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:30:07Z"
    - latency: 3.629166ms
      message: 'network-check-target-ip-10-0-128-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:29:07Z"
    - latency: 3.014606ms
      message: 'network-check-target-ip-10-0-128-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:28:07Z"
    - latency: 2.081502ms
      message: 'network-check-target-ip-10-0-128-164: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:27:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T19:19:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-104-to-network-check-target-ip-10-0-143-134
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-104.us-west-2.compute.internal
      uid: 1f3956b8-1ccf-4482-916d-03ab60194916
    resourceVersion: "112837"
    uid: 931e4c38-f586-42ff-8a94-4492deee4048
  spec:
    sourcePod: network-check-source-6f78d59f99-zkvsg
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T19:26:07Z"
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.241982ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:36:07Z"
    - latency: 2.492769ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:35:07Z"
    - latency: 2.502513ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:34:07Z"
    - latency: 2.33097ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:33:07Z"
    - latency: 2.397815ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:32:07Z"
    - latency: 2.519753ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:31:07Z"
    - latency: 2.564161ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:30:07Z"
    - latency: 4.670249ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:29:07Z"
    - latency: 1.959625ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:28:07Z"
    - latency: 2.569161ms
      message: 'network-check-target-ip-10-0-143-134: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:27:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T19:19:07Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-128-104-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-128-104.us-west-2.compute.internal
      uid: 1f3956b8-1ccf-4482-916d-03ab60194916
    resourceVersion: "113345"
    uid: 3ae74faa-854e-46e8-ad33-602496f94c2c
  spec:
    sourcePod: network-check-source-6f78d59f99-zkvsg
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T19:25:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.052731ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:37:07Z"
    - latency: 1.905834ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:37:07Z"
    - latency: 1.218691ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:36:07Z"
    - latency: 2.224865ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:36:07Z"
    - latency: 878.039µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:35:07Z"
    - latency: 2.417879ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:35:07Z"
    - latency: 1.028752ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:34:07Z"
    - latency: 1.947403ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:34:07Z"
    - latency: 847.455µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T20:33:07Z"
    - latency: 1.722089ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T20:33:07Z"
kind: List
metadata:
  resourceVersion: ""