apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:53:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-61-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-61.ec2.internal
      uid: bd992c76-a660-48d6-b5e9-155a33f1e0ae
    resourceVersion: "146315"
    uid: 1ac0d801-0266-4cd6-b585-daf167ba585e
  spec:
    sourcePod: network-check-source-6f78d59f99-68gnd
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:00:20Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.302499ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:56:20Z"
    - latency: 1.316402ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:55:20Z"
    - latency: 1.905409ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:54:20Z"
    - latency: 1.420689ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:53:20Z"
    - latency: 1.31935ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:52:20Z"
    - latency: 1.563521ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:51:20Z"
    - latency: 1.211796ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:50:20Z"
    - latency: 1.942794ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:49:20Z"
    - latency: 1.271302ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:48:20Z"
    - latency: 1.150567ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:47:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:53:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-61-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-61.ec2.internal
      uid: bd992c76-a660-48d6-b5e9-155a33f1e0ae
    resourceVersion: "148852"
    uid: 924e8392-c838-4a7a-b36e-5259e818ab3f
  spec:
    sourcePod: network-check-source-6f78d59f99-68gnd
    targetEndpoint: a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:59:20Z"
      message: 'load-balancer-api-external: tcp connection to a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.873434ms
      message: 'load-balancer-api-external: tcp connection to a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:59:20Z"
    - latency: 8.671063ms
      message: 'load-balancer-api-external: resolved host name a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:59:20Z"
    - latency: 15.977564ms
      message: 'load-balancer-api-external: tcp connection to a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:58:20Z"
    - latency: 7.833971ms
      message: 'load-balancer-api-external: resolved host name a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:58:20Z"
    - latency: 16.012801ms
      message: 'load-balancer-api-external: tcp connection to a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:57:20Z"
    - latency: 7.187005ms
      message: 'load-balancer-api-external: resolved host name a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:57:20Z"
    - latency: 16.242282ms
      message: 'load-balancer-api-external: tcp connection to a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:56:20Z"
    - latency: 6.674362ms
      message: 'load-balancer-api-external: resolved host name a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:56:20Z"
    - latency: 17.481719ms
      message: 'load-balancer-api-external: tcp connection to a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:55:20Z"
    - latency: 7.459955ms
      message: 'load-balancer-api-external: resolved host name a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:55:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:53:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-61-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-61.ec2.internal
      uid: bd992c76-a660-48d6-b5e9-155a33f1e0ae
    resourceVersion: "148851"
    uid: 2dfe5a49-80f2-4ef5-ae7d-8e5740c208bd
  spec:
    sourcePod: network-check-source-6f78d59f99-68gnd
    targetEndpoint: a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:59:20Z"
      message: 'load-balancer-api-internal: tcp connection to a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 16.876259ms
      message: 'load-balancer-api-internal: tcp connection to a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:59:20Z"
    - latency: 8.626454ms
      message: 'load-balancer-api-internal: resolved host name a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:59:20Z"
    - latency: 31.394051ms
      message: 'load-balancer-api-internal: tcp connection to a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:58:20Z"
    - latency: 7.806125ms
      message: 'load-balancer-api-internal: resolved host name a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:58:20Z"
    - latency: 16.292301ms
      message: 'load-balancer-api-internal: tcp connection to a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:57:20Z"
    - latency: 7.273667ms
      message: 'load-balancer-api-internal: resolved host name a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:57:20Z"
    - latency: 19.282929ms
      message: 'load-balancer-api-internal: tcp connection to a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:56:20Z"
    - latency: 6.739827ms
      message: 'load-balancer-api-internal: resolved host name a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:56:20Z"
    - latency: 15.719866ms
      message: 'load-balancer-api-internal: tcp connection to a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:55:20Z"
    - latency: 7.498751ms
      message: 'load-balancer-api-internal: resolved host name a7b072139ff3e4e9d825edc9b48c708d-f755e3cc5d1adfee.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:55:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:53:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-61-to-network-check-target-ip-10-0-133-61
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-61.ec2.internal
      uid: bd992c76-a660-48d6-b5e9-155a33f1e0ae
    resourceVersion: "146312"
    uid: 641445ea-077e-4bb1-8a7e-db2d6739025f
  spec:
    sourcePod: network-check-source-6f78d59f99-68gnd
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:00:20Z"
      message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.077758ms
      message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:56:20Z"
    - latency: 1.024435ms
      message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:55:20Z"
    - latency: 1.169858ms
      message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:54:20Z"
    - latency: 1.018261ms
      message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:53:20Z"
    - latency: 1.569176ms
      message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:52:20Z"
    - latency: 1.097009ms
      message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:51:20Z"
    - latency: 1.108998ms
      message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:50:20Z"
    - latency: 2.142164ms
      message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:49:20Z"
    - latency: 1.289646ms
      message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:48:20Z"
    - latency: 1.013098ms
      message: 'network-check-target-ip-10-0-133-61: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:47:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:53:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-61-to-network-check-target-ip-10-0-137-6
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-61.ec2.internal
      uid: bd992c76-a660-48d6-b5e9-155a33f1e0ae
    resourceVersion: "146314"
    uid: b0ed23fd-efc8-4473-b4b0-27eee5bb669d
  spec:
    sourcePod: network-check-source-6f78d59f99-68gnd
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:00:20Z"
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.464139ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:56:20Z"
    - latency: 2.704218ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:55:20Z"
    - latency: 2.926165ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:54:20Z"
    - latency: 2.022137ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:53:20Z"
    - latency: 2.265901ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:52:20Z"
    - latency: 1.823678ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:51:20Z"
    - latency: 2.464524ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:50:20Z"
    - latency: 3.792998ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:49:20Z"
    - latency: 2.300808ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:48:20Z"
    - latency: 2.314166ms
      message: 'network-check-target-ip-10-0-137-6: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:47:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:53:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-61-to-network-check-target-ip-10-0-138-103
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-61.ec2.internal
      uid: bd992c76-a660-48d6-b5e9-155a33f1e0ae
    resourceVersion: "146313"
    uid: a2aeb689-b53b-47a1-87bf-669127405f3f
  spec:
    sourcePod: network-check-source-6f78d59f99-68gnd
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T13:00:20Z"
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.400126ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:56:20Z"
    - latency: 2.185038ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:55:20Z"
    - latency: 2.648564ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:54:20Z"
    - latency: 1.93079ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:53:20Z"
    - latency: 2.12561ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:52:20Z"
    - latency: 1.901849ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:51:20Z"
    - latency: 2.136002ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:50:20Z"
    - latency: 3.011524ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:49:20Z"
    - latency: 2.108771ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:48:20Z"
    - latency: 1.851717ms
      message: 'network-check-target-ip-10-0-138-103: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:47:20Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T12:53:19Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-61-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-61.ec2.internal
      uid: bd992c76-a660-48d6-b5e9-155a33f1e0ae
    resourceVersion: "148850"
    uid: a55d5aba-36b3-473e-91b1-8cb47c141c80
  spec:
    sourcePod: network-check-source-6f78d59f99-68gnd
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T12:59:20Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.122333ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:59:20Z"
    - latency: 1.756143ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:59:20Z"
    - latency: 956.465µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:58:20Z"
    - latency: 1.821617ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:58:20Z"
    - latency: 1.560917ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:57:20Z"
    - latency: 1.974361ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:57:20Z"
    - latency: 872.199µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:56:20Z"
    - latency: 1.659584ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:56:20Z"
    - latency: 1.020437ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T13:55:20Z"
    - latency: 1.763717ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T13:55:20Z"
kind: List
metadata:
  resourceVersion: ""