apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T06:26:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-73-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-73.ec2.internal
      uid: 6a9eb78c-df44-4b06-8190-598d5c3b1447
    resourceVersion: "19429"
    uid: 3033e786-ab84-4ba3-a69a-bf8c0ad47c09
  spec:
    sourcePod: network-check-source-7f44b6dd87-wj292
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T06:33:38Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.108505ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:47:38Z"
    - latency: 1.085132ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:46:38Z"
    - latency: 980.766µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:45:38Z"
    - latency: 916.461µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:44:38Z"
    - latency: 1.000097ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:43:38Z"
    - latency: 1.142065ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:42:38Z"
    - latency: 1.06503ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:41:38Z"
    - latency: 1.087295ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:40:38Z"
    - latency: 1.139431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:39:38Z"
    - latency: 963.91µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:38:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T06:26:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-73-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-73.ec2.internal
      uid: 6a9eb78c-df44-4b06-8190-598d5c3b1447
    resourceVersion: "20625"
    uid: 333ab850-e0b8-49be-bf2b-374bc2dadd7e
  spec:
    sourcePod: network-check-source-7f44b6dd87-wj292
    targetEndpoint: a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T06:32:38Z"
      message: 'load-balancer-api-external: tcp connection to a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.427654ms
      message: 'load-balancer-api-external: tcp connection to a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:50:38Z"
    - latency: 6.2794ms
      message: 'load-balancer-api-external: resolved host name a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:50:38Z"
    - latency: 4.949588ms
      message: 'load-balancer-api-external: tcp connection to a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:49:38Z"
    - latency: 7.037201ms
      message: 'load-balancer-api-external: resolved host name a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:49:38Z"
    - latency: 6.246512ms
      message: 'load-balancer-api-external: tcp connection to a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:48:38Z"
    - latency: 7.969492ms
      message: 'load-balancer-api-external: resolved host name a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:48:38Z"
    - latency: 3.953274ms
      message: 'load-balancer-api-external: tcp connection to a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:47:38Z"
    - latency: 6.627817ms
      message: 'load-balancer-api-external: resolved host name a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:47:38Z"
    - latency: 5.742125ms
      message: 'load-balancer-api-external: tcp connection to a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:46:38Z"
    - latency: 6.355399ms
      message: 'load-balancer-api-external: resolved host name a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:46:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T06:26:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-73-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-73.ec2.internal
      uid: 6a9eb78c-df44-4b06-8190-598d5c3b1447
    resourceVersion: "20626"
    uid: 2f31779d-c306-4266-a43e-4f4382833fca
  spec:
    sourcePod: network-check-source-7f44b6dd87-wj292
    targetEndpoint: a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T06:32:38Z"
      message: 'load-balancer-api-internal: tcp connection to a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.837488ms
      message: 'load-balancer-api-internal: tcp connection to a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:50:38Z"
    - latency: 6.304655ms
      message: 'load-balancer-api-internal: resolved host name a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:50:38Z"
    - latency: 4.981393ms
      message: 'load-balancer-api-internal: tcp connection to a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:49:38Z"
    - latency: 6.98664ms
      message: 'load-balancer-api-internal: resolved host name a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:49:38Z"
    - latency: 6.28561ms
      message: 'load-balancer-api-internal: tcp connection to a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:48:38Z"
    - latency: 7.890712ms
      message: 'load-balancer-api-internal: resolved host name a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:48:38Z"
    - latency: 4.001281ms
      message: 'load-balancer-api-internal: tcp connection to a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:47:38Z"
    - latency: 6.571944ms
      message: 'load-balancer-api-internal: resolved host name a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:47:38Z"
    - latency: 5.804585ms
      message: 'load-balancer-api-internal: tcp connection to a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:46:38Z"
    - latency: 6.333613ms
      message: 'load-balancer-api-internal: resolved host name a3c499842a00a40c9956abcc63358c61-f8a37b1f94de4f79.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:46:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T06:26:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-73-to-network-check-target-ip-10-0-132-73
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-73.ec2.internal
      uid: 6a9eb78c-df44-4b06-8190-598d5c3b1447
    resourceVersion: "19426"
    uid: 60ae7f61-8368-4777-bdd9-a32a20cae4a6
  spec:
    sourcePod: network-check-source-7f44b6dd87-wj292
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T06:33:38Z"
      message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 880.147µs
      message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:47:38Z"
    - latency: 797.095µs
      message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:46:38Z"
    - latency: 862.212µs
      message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:45:38Z"
    - latency: 888.962µs
      message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:44:38Z"
    - latency: 945.485µs
      message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:43:38Z"
    - latency: 817.171µs
      message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:42:38Z"
    - latency: 1.23645ms
      message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:41:38Z"
    - latency: 895.431µs
      message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:40:38Z"
    - latency: 936.326µs
      message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:39:38Z"
    - latency: 799.495µs
      message: 'network-check-target-ip-10-0-132-73: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:38:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T06:26:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-73-to-network-check-target-ip-10-0-135-20
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-73.ec2.internal
      uid: 6a9eb78c-df44-4b06-8190-598d5c3b1447
    resourceVersion: "19428"
    uid: a29f1ad8-8ce2-4a70-81c6-f8c3a899645d
  spec:
    sourcePod: network-check-source-7f44b6dd87-wj292
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T06:33:38Z"
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.385413ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:47:38Z"
    - latency: 2.420587ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:46:38Z"
    - latency: 2.364543ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:45:38Z"
    - latency: 2.224476ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:44:38Z"
    - latency: 2.189035ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:43:38Z"
    - latency: 2.089347ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:42:38Z"
    - latency: 2.121799ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:41:38Z"
    - latency: 2.171923ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:40:38Z"
    - latency: 2.255172ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:39:38Z"
    - latency: 2.321823ms
      message: 'network-check-target-ip-10-0-135-20: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:38:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T06:26:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-73-to-network-check-target-ip-10-0-136-226
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-73.ec2.internal
      uid: 6a9eb78c-df44-4b06-8190-598d5c3b1447
    resourceVersion: "19427"
    uid: f146e710-aeab-4460-b167-1f2fa9ec31c7
  spec:
    sourcePod: network-check-source-7f44b6dd87-wj292
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T06:33:38Z"
      message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.346183ms
      message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:47:38Z"
    - latency: 2.063987ms
      message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:46:38Z"
    - latency: 2.22195ms
      message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:45:38Z"
    - latency: 2.182201ms
      message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:44:38Z"
    - latency: 2.363601ms
      message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:43:38Z"
    - latency: 2.167009ms
      message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:42:38Z"
    - latency: 2.430156ms
      message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:41:38Z"
    - latency: 2.345601ms
      message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:40:38Z"
    - latency: 2.363058ms
      message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:39:38Z"
    - latency: 2.025474ms
      message: 'network-check-target-ip-10-0-136-226: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:38:38Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-05-26T06:26:37Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-132-73-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-132-73.ec2.internal
      uid: 6a9eb78c-df44-4b06-8190-598d5c3b1447
    resourceVersion: "20624"
    uid: db3ba454-812a-401c-8213-2243c801cad5
  spec:
    sourcePod: network-check-source-7f44b6dd87-wj292
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-05-26T06:32:38Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 746.597µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:50:38Z"
    - latency: 1.72594ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:50:38Z"
    - latency: 922.81µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:49:38Z"
    - latency: 2.05048ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:49:38Z"
    - latency: 1.882823ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:48:38Z"
    - latency: 1.806541ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:48:38Z"
    - latency: 911.988µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:47:38Z"
    - latency: 1.646802ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:47:38Z"
    - latency: 851.934µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-05-26T06:46:38Z"
    - latency: 1.628896ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-05-26T06:46:38Z"
kind: List
metadata:
  resourceVersion: ""