apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T15:13:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-206-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-206.ec2.internal
      uid: 2a7b6097-f8df-4bf9-8901-248158b5139a
    resourceVersion: "30028"
    uid: 711cf550-1d39-467f-9249-c1e627157a33
  spec:
    sourcePod: network-check-source-6947749cfc-cpvkf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T15:20:16Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.014702ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:27:16Z"
    - latency: 1.50294ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:26:16Z"
    - latency: 1.034648ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:25:16Z"
    - latency: 910.736µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:24:16Z"
    - latency: 1.399765ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:23:16Z"
    - latency: 1.189427ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:22:16Z"
    - latency: 935.032µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:21:16Z"
    - latency: 1.713572ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:20:16Z"
    - latency: 947.252µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:19:16Z"
    - latency: 1.078191ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:18:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T15:13:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-206-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-206.ec2.internal
      uid: 2a7b6097-f8df-4bf9-8901-248158b5139a
    resourceVersion: "28759"
    uid: ecfb0faf-d1b2-4093-bf2f-0632317cd9e1
  spec:
    sourcePod: network-check-source-6947749cfc-cpvkf
    targetEndpoint: a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T15:19:16Z"
      message: 'load-balancer-api-external: tcp connection to a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.419423ms
      message: 'load-balancer-api-external: tcp connection to a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:25:16Z"
    - latency: 12.406548ms
      message: 'load-balancer-api-external: resolved host name a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:25:16Z"
    - latency: 5.245262ms
      message: 'load-balancer-api-external: tcp connection to a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:24:16Z"
    - latency: 14.708692ms
      message: 'load-balancer-api-external: resolved host name a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:24:16Z"
    - latency: 4.513095ms
      message: 'load-balancer-api-external: tcp connection to a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:23:16Z"
    - latency: 18.949688ms
      message: 'load-balancer-api-external: resolved host name a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:23:16Z"
    - latency: 4.485323ms
      message: 'load-balancer-api-external: tcp connection to a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:22:16Z"
    - latency: 9.620832ms
      message: 'load-balancer-api-external: resolved host name a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:22:16Z"
    - latency: 5.458876ms
      message: 'load-balancer-api-external: tcp connection to a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:21:16Z"
    - latency: 11.120411ms
      message: 'load-balancer-api-external: resolved host name a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:21:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T15:13:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-206-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-206.ec2.internal
      uid: 2a7b6097-f8df-4bf9-8901-248158b5139a
    resourceVersion: "28760"
    uid: b775a765-209d-4cfd-b176-d4b0362f0f48
  spec:
    sourcePod: network-check-source-6947749cfc-cpvkf
    targetEndpoint: a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T15:19:16Z"
      message: 'load-balancer-api-internal: tcp connection to a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.34356ms
      message: 'load-balancer-api-internal: tcp connection to a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:25:16Z"
    - latency: 12.375255ms
      message: 'load-balancer-api-internal: resolved host name a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:25:16Z"
    - latency: 8.979971ms
      message: 'load-balancer-api-internal: tcp connection to a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:24:16Z"
    - latency: 14.726406ms
      message: 'load-balancer-api-internal: resolved host name a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:24:16Z"
    - latency: 4.518811ms
      message: 'load-balancer-api-internal: tcp connection to a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:23:16Z"
    - latency: 18.963932ms
      message: 'load-balancer-api-internal: resolved host name a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:23:16Z"
    - latency: 5.413553ms
      message: 'load-balancer-api-internal: tcp connection to a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:22:16Z"
    - latency: 9.643102ms
      message: 'load-balancer-api-internal: resolved host name a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:22:16Z"
    - latency: 5.41664ms
      message: 'load-balancer-api-internal: tcp connection to a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:21:16Z"
    - latency: 11.18322ms
      message: 'load-balancer-api-internal: resolved host name a274ecd45bb71489880a4f0ea2a61caf-fc72546d0b1b3f21.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:21:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T15:13:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-206-to-network-check-target-ip-10-0-134-110
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-206.ec2.internal
      uid: 2a7b6097-f8df-4bf9-8901-248158b5139a
    resourceVersion: "30027"
    uid: 2eaaeddd-0391-48c2-9cdc-4cf70e07c404
  spec:
    sourcePod: network-check-source-6947749cfc-cpvkf
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T15:20:16Z"
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.40539ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:27:16Z"
    - latency: 2.416628ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:26:16Z"
    - latency: 2.209336ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:25:16Z"
    - latency: 2.189954ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:24:16Z"
    - latency: 2.29734ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:23:16Z"
    - latency: 2.616343ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:22:16Z"
    - latency: 1.975007ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:21:16Z"
    - latency: 2.196393ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:20:16Z"
    - latency: 2.317508ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:19:16Z"
    - latency: 2.036876ms
      message: 'network-check-target-ip-10-0-134-110: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:18:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T15:13:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-206-to-network-check-target-ip-10-0-136-206
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-206.ec2.internal
      uid: 2a7b6097-f8df-4bf9-8901-248158b5139a
    resourceVersion: "30024"
    uid: ae0391f2-adaa-49a8-85df-f0196463a3ca
  spec:
    sourcePod: network-check-source-6947749cfc-cpvkf
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T15:20:16Z"
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 965.163µs
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:27:16Z"
    - latency: 1.260736ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:26:16Z"
    - latency: 1.252926ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:25:16Z"
    - latency: 1.36111ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:24:16Z"
    - latency: 967.254µs
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:23:16Z"
    - latency: 1.283337ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:22:16Z"
    - latency: 994.347µs
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:21:16Z"
    - latency: 944.761µs
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:20:16Z"
    - latency: 1.076861ms
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:19:16Z"
    - latency: 978.164µs
      message: 'network-check-target-ip-10-0-136-206: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:18:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T15:13:15Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-206-to-network-check-target-ip-10-0-139-197
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-206.ec2.internal
      uid: 2a7b6097-f8df-4bf9-8901-248158b5139a
    resourceVersion: "30026"
    uid: 08d06211-644f-4942-ba59-c675f6a53375
  spec:
    sourcePod: network-check-source-6947749cfc-cpvkf
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T15:20:16Z"
      message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.389248ms
      message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:27:16Z"
    - latency: 2.353767ms
      message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:26:16Z"
    - latency: 2.186749ms
      message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:25:16Z"
    - latency: 2.542357ms
      message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:24:16Z"
    - latency: 2.495446ms
      message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:23:16Z"
    - latency: 2.80469ms
      message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:22:16Z"
    - latency: 2.445ms
      message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:21:16Z"
    - latency: 2.558896ms
      message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:20:16Z"
    - latency: 2.328997ms
      message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:19:16Z"
    - latency: 2.008541ms
      message: 'network-check-target-ip-10-0-139-197: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:18:16Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-06-15T15:13:16Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-206-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-206.ec2.internal
      uid: 2a7b6097-f8df-4bf9-8901-248158b5139a
    resourceVersion: "28758"
    uid: 194a6b78-2f81-422e-b62b-f31c540bebbf
  spec:
    sourcePod: network-check-source-6947749cfc-cpvkf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-06-15T15:19:16Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.020415ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:25:16Z"
    - latency: 1.694871ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:25:16Z"
    - latency: 1.114265ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:24:16Z"
    - latency: 1.680494ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:24:16Z"
    - latency: 869.039µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:23:16Z"
    - latency: 1.80259ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:23:16Z"
    - latency: 991.641µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:22:16Z"
    - latency: 1.862931ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:22:16Z"
    - latency: 855.823µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-06-15T15:21:16Z"
    - latency: 1.883616ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-06-15T15:21:16Z"
kind: List
metadata:
  resourceVersion: ""