apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T16:04:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-127-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-127.us-west-2.compute.internal
      uid: f253db34-638c-4510-9de1-db414e165bcc
    resourceVersion: "105661"
    uid: fbe34344-20e8-4177-bc2f-b78c5aa52267
  spec:
    sourcePod: network-check-source-6f78d59f99-hlsdq
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T16:11:05Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.265788ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:07:05Z"
    - latency: 1.149328ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:06:05Z"
    - latency: 1.348033ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:05:05Z"
    - latency: 964.158µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:04:05Z"
    - latency: 1.150186ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:03:05Z"
    - latency: 1.194297ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:02:05Z"
    - latency: 1.331058ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:01:05Z"
    - latency: 1.194908ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:00:05Z"
    - latency: 1.356538ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T16:59:05Z"
    - latency: 1.169274ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T16:58:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T16:04:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-127-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-127.us-west-2.compute.internal
      uid: f253db34-638c-4510-9de1-db414e165bcc
    resourceVersion: "108341"
    uid: ae4b9de2-4689-44fe-842f-fa0aef712492
  spec:
    sourcePod: network-check-source-6f78d59f99-hlsdq
    targetEndpoint: a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T16:10:05Z"
      message: 'load-balancer-api-external: tcp connection to a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.249106ms
      message: 'load-balancer-api-external: tcp connection to a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:10:05Z"
    - latency: 11.04119ms
      message: 'load-balancer-api-external: resolved host name a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:10:05Z"
    - latency: 54.666096ms
      message: 'load-balancer-api-external: tcp connection to a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:09:05Z"
    - latency: 6.533643ms
      message: 'load-balancer-api-external: resolved host name a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:09:05Z"
    - latency: 55.657211ms
      message: 'load-balancer-api-external: tcp connection to a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:08:05Z"
    - latency: 7.12855ms
      message: 'load-balancer-api-external: resolved host name a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:08:05Z"
    - latency: 50.57401ms
      message: 'load-balancer-api-external: tcp connection to a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:07:05Z"
    - latency: 7.524672ms
      message: 'load-balancer-api-external: resolved host name a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:07:05Z"
    - latency: 52.040159ms
      message: 'load-balancer-api-external: tcp connection to a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:06:05Z"
    - latency: 6.75177ms
      message: 'load-balancer-api-external: resolved host name a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:06:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T16:04:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-127-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-127.us-west-2.compute.internal
      uid: f253db34-638c-4510-9de1-db414e165bcc
    resourceVersion: "108340"
    uid: 48d6ed66-d39a-4ff3-8e33-f3955770b3c1
  spec:
    sourcePod: network-check-source-6f78d59f99-hlsdq
    targetEndpoint: a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T16:10:05Z"
      message: 'load-balancer-api-internal: tcp connection to a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 55.383512ms
      message: 'load-balancer-api-internal: tcp connection to a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:10:05Z"
    - latency: 10.989871ms
      message: 'load-balancer-api-internal: resolved host name a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:10:05Z"
    - latency: 50.927812ms
      message: 'load-balancer-api-internal: tcp connection to a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:09:05Z"
    - latency: 6.546993ms
      message: 'load-balancer-api-internal: resolved host name a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:09:05Z"
    - latency: 55.870863ms
      message: 'load-balancer-api-internal: tcp connection to a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:08:05Z"
    - latency: 7.118613ms
      message: 'load-balancer-api-internal: resolved host name a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:08:05Z"
    - latency: 53.985671ms
      message: 'load-balancer-api-internal: tcp connection to a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:07:05Z"
    - latency: 7.47767ms
      message: 'load-balancer-api-internal: resolved host name a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:07:05Z"
    - latency: 55.922181ms
      message: 'load-balancer-api-internal: tcp connection to a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:06:05Z"
    - latency: 6.774041ms
      message: 'load-balancer-api-internal: resolved host name a7918a53732334b8eb1150a335f38936-a35c44805d999c48.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:06:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T16:04:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-127-to-network-check-target-ip-10-0-129-180
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-127.us-west-2.compute.internal
      uid: f253db34-638c-4510-9de1-db414e165bcc
    resourceVersion: "105655"
    uid: 99d42b49-f1b0-457a-952a-ed0c09aca765
  spec:
    sourcePod: network-check-source-6f78d59f99-hlsdq
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T16:11:05Z"
      message: 'network-check-target-ip-10-0-129-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.797138ms
      message: 'network-check-target-ip-10-0-129-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:07:05Z"
    - latency: 1.812897ms
      message: 'network-check-target-ip-10-0-129-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:06:05Z"
    - latency: 2.020372ms
      message: 'network-check-target-ip-10-0-129-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:05:05Z"
    - latency: 2.017676ms
      message: 'network-check-target-ip-10-0-129-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:04:05Z"
    - latency: 2.22719ms
      message: 'network-check-target-ip-10-0-129-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:03:05Z"
    - latency: 1.996853ms
      message: 'network-check-target-ip-10-0-129-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:02:05Z"
    - latency: 1.847888ms
      message: 'network-check-target-ip-10-0-129-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:01:05Z"
    - latency: 2.290666ms
      message: 'network-check-target-ip-10-0-129-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:00:05Z"
    - latency: 2.110699ms
      message: 'network-check-target-ip-10-0-129-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T16:59:05Z"
    - latency: 2.200882ms
      message: 'network-check-target-ip-10-0-129-180: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T16:58:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T16:04:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-127-to-network-check-target-ip-10-0-140-84
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-127.us-west-2.compute.internal
      uid: f253db34-638c-4510-9de1-db414e165bcc
    resourceVersion: "105656"
    uid: f35b3519-234d-4243-bbb5-59fe31cc77b3
  spec:
    sourcePod: network-check-source-6f78d59f99-hlsdq
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T16:11:05Z"
      message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.069923ms
      message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:07:05Z"
    - latency: 2.654724ms
      message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:06:05Z"
    - latency: 2.283963ms
      message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:05:05Z"
    - latency: 2.112143ms
      message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:04:05Z"
    - latency: 1.915647ms
      message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:03:05Z"
    - latency: 2.17648ms
      message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:02:05Z"
    - latency: 2.475375ms
      message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:01:05Z"
    - latency: 2.253334ms
      message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:00:05Z"
    - latency: 2.275424ms
      message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T16:59:05Z"
    - latency: 2.352598ms
      message: 'network-check-target-ip-10-0-140-84: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T16:58:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T16:04:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-127-to-network-check-target-ip-10-0-142-127
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-127.us-west-2.compute.internal
      uid: f253db34-638c-4510-9de1-db414e165bcc
    resourceVersion: "105662"
    uid: 4f027365-79f9-4191-be60-01ce8db1d201
  spec:
    sourcePod: network-check-source-6f78d59f99-hlsdq
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T16:11:05Z"
      message: 'network-check-target-ip-10-0-142-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.322955ms
      message: 'network-check-target-ip-10-0-142-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:07:05Z"
    - latency: 981.49µs
      message: 'network-check-target-ip-10-0-142-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:06:05Z"
    - latency: 1.0767ms
      message: 'network-check-target-ip-10-0-142-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:05:05Z"
    - latency: 1.189576ms
      message: 'network-check-target-ip-10-0-142-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:04:05Z"
    - latency: 881.394µs
      message: 'network-check-target-ip-10-0-142-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:03:05Z"
    - latency: 1.559622ms
      message: 'network-check-target-ip-10-0-142-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:02:05Z"
    - latency: 1.059065ms
      message: 'network-check-target-ip-10-0-142-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:01:05Z"
    - latency: 1.012547ms
      message: 'network-check-target-ip-10-0-142-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:00:05Z"
    - latency: 776.884µs
      message: 'network-check-target-ip-10-0-142-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T16:59:05Z"
    - latency: 1.281536ms
      message: 'network-check-target-ip-10-0-142-127: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T16:58:05Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-31T16:04:05Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-142-127-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-142-127.us-west-2.compute.internal
      uid: f253db34-638c-4510-9de1-db414e165bcc
    resourceVersion: "108338"
    uid: 20285790-ecf6-4825-9aa6-86770a219ff2
  spec:
    sourcePod: network-check-source-6f78d59f99-hlsdq
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-31T16:10:05Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 831.249µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:10:05Z"
    - latency: 556.605µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:10:05Z"
    - latency: 1.047681ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:09:05Z"
    - latency: 553.676µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:09:05Z"
    - latency: 923.058µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:08:05Z"
    - latency: 570.783µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:08:05Z"
    - latency: 870.518µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:07:05Z"
    - latency: 532.035µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:07:05Z"
    - latency: 1.08406ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-31T17:06:05Z"
    - latency: 532.794µs
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-31T17:06:05Z"
kind: List
metadata:
  resourceVersion: ""