apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T21:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-216-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-216.ec2.internal
      uid: f54d453e-b4ba-4de6-97c7-3c4e7c7a4c43
    resourceVersion: "46571"
    uid: 2e2408da-5949-40a3-8777-0dc89b90591f
  spec:
    sourcePod: network-check-source-dbd9cf844-vgvpw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T21:13:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 988.07µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:34:11Z"
    - latency: 910.285µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:33:11Z"
    - latency: 1.078079ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:32:11Z"
    - latency: 1.055919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:31:11Z"
    - latency: 1.128397ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:30:11Z"
    - latency: 849.683µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:29:11Z"
    - latency: 915.641µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:28:11Z"
    - latency: 865.645µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:27:11Z"
    - latency: 912.061µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:26:11Z"
    - latency: 1.030369ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:25:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T21:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-216-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-216.ec2.internal
      uid: f54d453e-b4ba-4de6-97c7-3c4e7c7a4c43
    resourceVersion: "48683"
    uid: 28a533c7-cf1e-4d1f-b5f4-b45c28a4da63
  spec:
    sourcePod: network-check-source-dbd9cf844-vgvpw
    targetEndpoint: a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T21:12:11Z"
      message: 'load-balancer-api-external: tcp connection to a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.134782ms
      message: 'load-balancer-api-external: tcp connection to a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:36:11Z"
    - latency: 9.622983ms
      message: 'load-balancer-api-external: resolved host name a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:36:11Z"
    - latency: 4.075202ms
      message: 'load-balancer-api-external: tcp connection to a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:35:11Z"
    - latency: 8.111917ms
      message: 'load-balancer-api-external: resolved host name a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:35:11Z"
    - latency: 2.949552ms
      message: 'load-balancer-api-external: tcp connection to a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:34:11Z"
    - latency: 11.897812ms
      message: 'load-balancer-api-external: resolved host name a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:34:11Z"
    - latency: 5.774698ms
      message: 'load-balancer-api-external: tcp connection to a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:33:11Z"
    - latency: 10.102834ms
      message: 'load-balancer-api-external: resolved host name a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:33:11Z"
    - latency: 5.346993ms
      message: 'load-balancer-api-external: tcp connection to a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:32:11Z"
    - latency: 8.683278ms
      message: 'load-balancer-api-external: resolved host name a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:32:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T21:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-216-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-216.ec2.internal
      uid: f54d453e-b4ba-4de6-97c7-3c4e7c7a4c43
    resourceVersion: "48684"
    uid: a8d970a0-4fa0-4750-b72f-f2b6df7e681e
  spec:
    sourcePod: network-check-source-dbd9cf844-vgvpw
    targetEndpoint: a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T21:12:11Z"
      message: 'load-balancer-api-internal: tcp connection to a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.176095ms
      message: 'load-balancer-api-internal: tcp connection to a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:36:11Z"
    - latency: 9.602191ms
      message: 'load-balancer-api-internal: resolved host name a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:36:11Z"
    - latency: 4.315451ms
      message: 'load-balancer-api-internal: tcp connection to a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:35:11Z"
    - latency: 8.013993ms
      message: 'load-balancer-api-internal: resolved host name a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:35:11Z"
    - latency: 2.695064ms
      message: 'load-balancer-api-internal: tcp connection to a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:34:11Z"
    - latency: 11.85067ms
      message: 'load-balancer-api-internal: resolved host name a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:34:11Z"
    - latency: 5.768473ms
      message: 'load-balancer-api-internal: tcp connection to a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:33:11Z"
    - latency: 10.129709ms
      message: 'load-balancer-api-internal: resolved host name a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:33:11Z"
    - latency: 5.349104ms
      message: 'load-balancer-api-internal: tcp connection to a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:32:11Z"
    - latency: 8.627234ms
      message: 'load-balancer-api-internal: resolved host name a79cec194e74847b98796c1236ff6b4b-30e7b06d8c1ee861.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:32:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T21:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-216-to-network-check-target-ip-10-0-135-120
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-216.ec2.internal
      uid: f54d453e-b4ba-4de6-97c7-3c4e7c7a4c43
    resourceVersion: "46570"
    uid: 9f6cf7e2-2e92-4b2e-95d5-f3ebc0155000
  spec:
    sourcePod: network-check-source-dbd9cf844-vgvpw
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T21:13:11Z"
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.199546ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:34:11Z"
    - latency: 2.760044ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:33:11Z"
    - latency: 2.247196ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:32:11Z"
    - latency: 2.391333ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:31:11Z"
    - latency: 2.508376ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:30:11Z"
    - latency: 2.636103ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:29:11Z"
    - latency: 2.235369ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:28:11Z"
    - latency: 1.933078ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:27:11Z"
    - latency: 2.228452ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:26:11Z"
    - latency: 2.307597ms
      message: 'network-check-target-ip-10-0-135-120: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:25:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T21:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-216-to-network-check-target-ip-10-0-139-216
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-216.ec2.internal
      uid: f54d453e-b4ba-4de6-97c7-3c4e7c7a4c43
    resourceVersion: "46568"
    uid: c11fe988-16e3-4c95-8651-d0d4abcd8a65
  spec:
    sourcePod: network-check-source-dbd9cf844-vgvpw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T21:13:11Z"
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 842.946µs
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:34:11Z"
    - latency: 1.365568ms
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:33:11Z"
    - latency: 768.492µs
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:32:11Z"
    - latency: 781.904µs
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:31:11Z"
    - latency: 1.276868ms
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:30:11Z"
    - latency: 1.459073ms
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:29:11Z"
    - latency: 1.450932ms
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:28:11Z"
    - latency: 853.72µs
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:27:11Z"
    - latency: 993.732µs
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:26:11Z"
    - latency: 823.412µs
      message: 'network-check-target-ip-10-0-139-216: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:25:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T21:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-216-to-network-check-target-ip-10-0-142-79
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-216.ec2.internal
      uid: f54d453e-b4ba-4de6-97c7-3c4e7c7a4c43
    resourceVersion: "46569"
    uid: 7a11b9e5-bd35-4da8-98f5-744c223da2e6
  spec:
    sourcePod: network-check-source-dbd9cf844-vgvpw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T21:13:11Z"
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.696962ms
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:34:11Z"
    - latency: 2.217832ms
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:33:11Z"
    - latency: 1.872659ms
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:32:11Z"
    - latency: 2.679475ms
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:31:11Z"
    - latency: 2.271468ms
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:30:11Z"
    - latency: 1.82554ms
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:29:11Z"
    - latency: 1.621293ms
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:28:11Z"
    - latency: 2.104853ms
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:27:11Z"
    - latency: 1.706114ms
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:26:11Z"
    - latency: 2.242249ms
      message: 'network-check-target-ip-10-0-142-79: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:25:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-03T21:06:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-216-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-216.ec2.internal
      uid: f54d453e-b4ba-4de6-97c7-3c4e7c7a4c43
    resourceVersion: "48682"
    uid: 75b8da2d-06de-44b0-a1ca-28e3aeb43fa8
  spec:
    sourcePod: network-check-source-dbd9cf844-vgvpw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-03T21:12:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.048161ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:36:11Z"
    - latency: 2.106427ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:36:11Z"
    - latency: 824.707µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:35:11Z"
    - latency: 1.583565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:35:11Z"
    - latency: 925.697µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:34:11Z"
    - latency: 2.034009ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:34:11Z"
    - latency: 925.681µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:33:11Z"
    - latency: 1.770758ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:33:11Z"
    - latency: 1.010423ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-03T21:32:11Z"
    - latency: 1.778595ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-03T21:32:11Z"
kind: List
metadata:
  resourceVersion: ""