apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T13:45:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-60-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-60.us-east-2.compute.internal
      uid: 71faddaf-86bd-4dd0-9e25-00e7676310a7
    resourceVersion: "74230"
    uid: 8df2e5ec-3d17-410d-afd5-cb40dd0b9b2c
  spec:
    sourcePod: network-check-source-6f78d59f99-lmrl4
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T13:52:37Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.275046ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:20:37Z"
    - latency: 1.0439ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:19:37Z"
    - latency: 1.521488ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:18:37Z"
    - latency: 1.504333ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:17:37Z"
    - latency: 923.342µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:16:37Z"
    - latency: 1.777632ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:15:37Z"
    - latency: 1.372652ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:14:37Z"
    - latency: 939.47µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:13:37Z"
    - latency: 1.197113ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:12:37Z"
    - latency: 1.4283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:11:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T13:45:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-60-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-60.us-east-2.compute.internal
      uid: 71faddaf-86bd-4dd0-9e25-00e7676310a7
    resourceVersion: "69157"
    uid: 1e4501b8-572c-42cf-aed0-27c5fd8574fc
  spec:
    sourcePod: network-check-source-6f78d59f99-lmrl4
    targetEndpoint: a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T13:51:37Z"
      message: 'load-balancer-api-external: tcp connection to a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.921561ms
      message: 'load-balancer-api-external: tcp connection to a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:15:37Z"
    - latency: 10.347745ms
      message: 'load-balancer-api-external: resolved host name a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:15:37Z"
    - latency: 5.015431ms
      message: 'load-balancer-api-external: tcp connection to a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:14:37Z"
    - latency: 7.422948ms
      message: 'load-balancer-api-external: resolved host name a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:14:37Z"
    - latency: 5.473097ms
      message: 'load-balancer-api-external: tcp connection to a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:13:37Z"
    - latency: 6.775356ms
      message: 'load-balancer-api-external: resolved host name a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:13:37Z"
    - latency: 5.390319ms
      message: 'load-balancer-api-external: tcp connection to a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:12:37Z"
    - latency: 6.828949ms
      message: 'load-balancer-api-external: resolved host name a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:12:37Z"
    - latency: 6.179444ms
      message: 'load-balancer-api-external: tcp connection to a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:11:37Z"
    - latency: 6.565904ms
      message: 'load-balancer-api-external: resolved host name a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:11:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T13:45:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-60-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-60.us-east-2.compute.internal
      uid: 71faddaf-86bd-4dd0-9e25-00e7676310a7
    resourceVersion: "69158"
    uid: 7002c158-5400-461d-a9c1-b7947e0ac830
  spec:
    sourcePod: network-check-source-6f78d59f99-lmrl4
    targetEndpoint: a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T13:51:37Z"
      message: 'load-balancer-api-internal: tcp connection to a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 14.148451ms
      message: 'load-balancer-api-internal: tcp connection to a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:15:37Z"
    - latency: 10.130889ms
      message: 'load-balancer-api-internal: resolved host name a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:15:37Z"
    - latency: 5.500937ms
      message: 'load-balancer-api-internal: tcp connection to a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:14:37Z"
    - latency: 7.371704ms
      message: 'load-balancer-api-internal: resolved host name a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:14:37Z"
    - latency: 5.175072ms
      message: 'load-balancer-api-internal: tcp connection to a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:13:37Z"
    - latency: 6.811491ms
      message: 'load-balancer-api-internal: resolved host name a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:13:37Z"
    - latency: 5.438962ms
      message: 'load-balancer-api-internal: tcp connection to a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:12:37Z"
    - latency: 6.779061ms
      message: 'load-balancer-api-internal: resolved host name a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:12:37Z"
    - latency: 6.972744ms
      message: 'load-balancer-api-internal: tcp connection to a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:11:37Z"
    - latency: 6.527176ms
      message: 'load-balancer-api-internal: resolved host name a2a16a09ecc554827bab4d7aefffc7a3-f751b33f3734e270.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:11:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T13:45:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-60-to-network-check-target-ip-10-0-128-62
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-60.us-east-2.compute.internal
      uid: 71faddaf-86bd-4dd0-9e25-00e7676310a7
    resourceVersion: "74228"
    uid: 723585b7-1f65-404b-91c3-f5d98d7fc72f
  spec:
    sourcePod: network-check-source-6f78d59f99-lmrl4
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T13:52:37Z"
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.422895ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:20:37Z"
    - latency: 2.341109ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:19:37Z"
    - latency: 2.390063ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:18:37Z"
    - latency: 2.373658ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:17:37Z"
    - latency: 2.360377ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:16:37Z"
    - latency: 3.938784ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:15:37Z"
    - latency: 2.65146ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:14:37Z"
    - latency: 2.176108ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:13:37Z"
    - latency: 2.623901ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:12:37Z"
    - latency: 2.523736ms
      message: 'network-check-target-ip-10-0-128-62: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:11:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T13:45:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-60-to-network-check-target-ip-10-0-131-166
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-60.us-east-2.compute.internal
      uid: 71faddaf-86bd-4dd0-9e25-00e7676310a7
    resourceVersion: "74227"
    uid: 1f8b2ad8-6374-4f42-9baa-2e80aa32a092
  spec:
    sourcePod: network-check-source-6f78d59f99-lmrl4
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T13:52:37Z"
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.321609ms
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:20:37Z"
    - latency: 2.23073ms
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:19:37Z"
    - latency: 2.221996ms
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:18:37Z"
    - latency: 2.440671ms
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:17:37Z"
    - latency: 2.363695ms
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:16:37Z"
    - latency: 3.291431ms
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:15:37Z"
    - latency: 2.574376ms
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:14:37Z"
    - latency: 1.945637ms
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:13:37Z"
    - latency: 2.006539ms
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:12:37Z"
    - latency: 2.265374ms
      message: 'network-check-target-ip-10-0-131-166: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:11:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T13:45:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-60-to-network-check-target-ip-10-0-134-60
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-60.us-east-2.compute.internal
      uid: 71faddaf-86bd-4dd0-9e25-00e7676310a7
    resourceVersion: "74226"
    uid: a432139e-d4d8-4489-b9c1-1c19586148ad
  spec:
    sourcePod: network-check-source-6f78d59f99-lmrl4
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T13:52:37Z"
      message: 'network-check-target-ip-10-0-134-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 977.095µs
      message: 'network-check-target-ip-10-0-134-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:20:37Z"
    - latency: 974.137µs
      message: 'network-check-target-ip-10-0-134-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:19:37Z"
    - latency: 1.243299ms
      message: 'network-check-target-ip-10-0-134-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:18:37Z"
    - latency: 924.729µs
      message: 'network-check-target-ip-10-0-134-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:17:37Z"
    - latency: 894.691µs
      message: 'network-check-target-ip-10-0-134-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:16:37Z"
    - latency: 2.578336ms
      message: 'network-check-target-ip-10-0-134-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:15:37Z"
    - latency: 1.011081ms
      message: 'network-check-target-ip-10-0-134-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:14:37Z"
    - latency: 1.030208ms
      message: 'network-check-target-ip-10-0-134-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:13:37Z"
    - latency: 1.218364ms
      message: 'network-check-target-ip-10-0-134-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:12:37Z"
    - latency: 1.276989ms
      message: 'network-check-target-ip-10-0-134-60: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:11:37Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-02T13:45:36Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-60-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-60.us-east-2.compute.internal
      uid: 71faddaf-86bd-4dd0-9e25-00e7676310a7
    resourceVersion: "69156"
    uid: 36c46e36-bd2b-4e9d-ae75-b7ef87762f64
  spec:
    sourcePod: network-check-source-6f78d59f99-lmrl4
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-02T13:51:37Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.018135ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:15:37Z"
    - latency: 4.158675ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:15:37Z"
    - latency: 1.378436ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:14:37Z"
    - latency: 1.960945ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:14:37Z"
    - latency: 1.136464ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:13:37Z"
    - latency: 2.112264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:13:37Z"
    - latency: 1.045568ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:12:37Z"
    - latency: 2.105014ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:12:37Z"
    - latency: 918.521µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-02T14:11:37Z"
    - latency: 1.759985ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-02T14:11:37Z"
kind: List
metadata:
  resourceVersion: ""