apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:10:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-23-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-23.us-west-1.compute.internal
      uid: af03d808-afab-4a0c-ac10-c339602835aa
    resourceVersion: "93824"
    uid: b4293790-9926-45c1-9031-89a9c3a59906
  spec:
    sourcePod: network-check-source-6f78d59f99-qmkmp
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:17:10Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.046298ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:06:09Z"
    - latency: 877.406µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:05:09Z"
    - latency: 1.179412ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:04:09Z"
    - latency: 1.564389ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:03:09Z"
    - latency: 1.10918ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:02:09Z"
    - latency: 1.078662ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:01:09Z"
    - latency: 979.628µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:00:09Z"
    - latency: 1.164001ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:59:09Z"
    - latency: 1.480042ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:58:09Z"
    - latency: 1.121027ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:57:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:10:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-23-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-23.us-west-1.compute.internal
      uid: af03d808-afab-4a0c-ac10-c339602835aa
    resourceVersion: "97667"
    uid: e78ba4ca-305f-41cf-8b05-50595d0f0e23
  spec:
    sourcePod: network-check-source-6f78d59f99-qmkmp
    targetEndpoint: a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:16:10Z"
      message: 'load-balancer-api-external: tcp connection to a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.346186ms
      message: 'load-balancer-api-external: tcp connection to a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:10:09Z"
    - latency: 67.589519ms
      message: 'load-balancer-api-external: resolved host name a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:10:09Z"
    - latency: 54.182695ms
      message: 'load-balancer-api-external: tcp connection to a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:09:09Z"
    - latency: 5.795949ms
      message: 'load-balancer-api-external: resolved host name a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:09:09Z"
    - latency: 53.43436ms
      message: 'load-balancer-api-external: tcp connection to a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:08:09Z"
    - latency: 6.919734ms
      message: 'load-balancer-api-external: resolved host name a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:08:09Z"
    - latency: 54.668272ms
      message: 'load-balancer-api-external: tcp connection to a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:07:09Z"
    - latency: 8.249095ms
      message: 'load-balancer-api-external: resolved host name a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:07:09Z"
    - latency: 53.289243ms
      message: 'load-balancer-api-external: tcp connection to a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:06:09Z"
    - latency: 7.080451ms
      message: 'load-balancer-api-external: resolved host name a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:06:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:10:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-23-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-23.us-west-1.compute.internal
      uid: af03d808-afab-4a0c-ac10-c339602835aa
    resourceVersion: "97666"
    uid: 13b8739f-e927-447f-bd80-c8ff3c79bb34
  spec:
    sourcePod: network-check-source-6f78d59f99-qmkmp
    targetEndpoint: a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:16:12Z"
      message: 'load-balancer-api-internal: tcp connection to a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 56.959327ms
      message: 'load-balancer-api-internal: tcp connection to a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:10:09Z"
    - latency: 66.559948ms
      message: 'load-balancer-api-internal: resolved host name a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:10:09Z"
    - latency: 54.198105ms
      message: 'load-balancer-api-internal: tcp connection to a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:09:09Z"
    - latency: 5.889267ms
      message: 'load-balancer-api-internal: resolved host name a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:09:09Z"
    - latency: 53.021113ms
      message: 'load-balancer-api-internal: tcp connection to a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:08:09Z"
    - latency: 6.971484ms
      message: 'load-balancer-api-internal: resolved host name a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:08:09Z"
    - latency: 54.021432ms
      message: 'load-balancer-api-internal: tcp connection to a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:07:09Z"
    - latency: 8.316486ms
      message: 'load-balancer-api-internal: resolved host name a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:07:09Z"
    - latency: 53.277341ms
      message: 'load-balancer-api-internal: tcp connection to a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:06:09Z"
    - latency: 7.107467ms
      message: 'load-balancer-api-internal: resolved host name a2ce9ff9192244e67a5502d625692119-459a7f00d10b34a9.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:06:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:10:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-23-to-network-check-target-ip-10-0-134-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-23.us-west-1.compute.internal
      uid: af03d808-afab-4a0c-ac10-c339602835aa
    resourceVersion: "93820"
    uid: faa41090-dd3f-4253-9f48-01e690f22192
  spec:
    sourcePod: network-check-source-6f78d59f99-qmkmp
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:17:09Z"
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.155479ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:06:09Z"
    - latency: 948.084µs
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:05:09Z"
    - latency: 1.497549ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:04:09Z"
    - latency: 1.104024ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:03:09Z"
    - latency: 1.308723ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:02:09Z"
    - latency: 1.023269ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:01:09Z"
    - latency: 840.672µs
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:00:09Z"
    - latency: 1.338053ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:59:09Z"
    - latency: 1.174514ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:58:09Z"
    - latency: 1.029125ms
      message: 'network-check-target-ip-10-0-134-23: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:57:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:10:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-23-to-network-check-target-ip-10-0-139-207
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-23.us-west-1.compute.internal
      uid: af03d808-afab-4a0c-ac10-c339602835aa
    resourceVersion: "93821"
    uid: 4c2a35e4-00f7-420f-beaa-9d68a8316acc
  spec:
    sourcePod: network-check-source-6f78d59f99-qmkmp
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:17:09Z"
      message: 'network-check-target-ip-10-0-139-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.10951ms
      message: 'network-check-target-ip-10-0-139-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:06:09Z"
    - latency: 1.885353ms
      message: 'network-check-target-ip-10-0-139-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:05:09Z"
    - latency: 1.975916ms
      message: 'network-check-target-ip-10-0-139-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:04:09Z"
    - latency: 2.244495ms
      message: 'network-check-target-ip-10-0-139-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:03:09Z"
    - latency: 2.001142ms
      message: 'network-check-target-ip-10-0-139-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:02:09Z"
    - latency: 1.929746ms
      message: 'network-check-target-ip-10-0-139-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:01:09Z"
    - latency: 1.846634ms
      message: 'network-check-target-ip-10-0-139-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:00:09Z"
    - latency: 2.104984ms
      message: 'network-check-target-ip-10-0-139-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:59:09Z"
    - latency: 2.302915ms
      message: 'network-check-target-ip-10-0-139-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:58:09Z"
    - latency: 2.114038ms
      message: 'network-check-target-ip-10-0-139-207: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:57:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:10:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-23-to-network-check-target-ip-10-0-139-35
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-23.us-west-1.compute.internal
      uid: af03d808-afab-4a0c-ac10-c339602835aa
    resourceVersion: "93822"
    uid: 42c8dbdc-0f8f-4e37-b343-2d9ea918264f
  spec:
    sourcePod: network-check-source-6f78d59f99-qmkmp
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:17:09Z"
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.345464ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:06:09Z"
    - latency: 2.21149ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:05:09Z"
    - latency: 2.352102ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:04:09Z"
    - latency: 2.37101ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:03:09Z"
    - latency: 1.973788ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:02:09Z"
    - latency: 2.279746ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:01:09Z"
    - latency: 2.267125ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:00:09Z"
    - latency: 2.238615ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:59:09Z"
    - latency: 1.983233ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:58:09Z"
    - latency: 2.282808ms
      message: 'network-check-target-ip-10-0-139-35: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T15:57:09Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T15:10:09Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-23-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-23.us-west-1.compute.internal
      uid: af03d808-afab-4a0c-ac10-c339602835aa
    resourceVersion: "97661"
    uid: f1ee6a5b-630c-48d4-90c1-af9cde206453
  spec:
    sourcePod: network-check-source-6f78d59f99-qmkmp
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T15:16:09Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 11.155753ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:10:09Z"
    - latency: 18.673267ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:10:09Z"
    - latency: 819.347µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:09:09Z"
    - latency: 1.685535ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:09:09Z"
    - latency: 1.019876ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:08:09Z"
    - latency: 2.250655ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:08:09Z"
    - latency: 1.000643ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:07:09Z"
    - latency: 1.88508ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:07:09Z"
    - latency: 731.26µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T16:06:09Z"
    - latency: 2.410757ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T16:06:09Z"
kind: List
metadata:
  resourceVersion: ""