apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:41:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-85-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-85.us-west-1.compute.internal
      uid: 6fd57672-a7f8-4e06-b40d-89a2333677be
    resourceVersion: "105105"
    uid: 2e79d35a-f315-4d57-ae6d-c052bf246f11
  spec:
    sourcePod: network-check-source-6f78d59f99-gqbfm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:48:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.130949ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 1.385872ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 999.173µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:29Z"
    - latency: 1.333788ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:29Z"
    - latency: 984.056µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:29Z"
    - latency: 1.257518ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:29Z"
    - latency: 1.283323ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:38:29Z"
    - latency: 1.146805ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:37:29Z"
    - latency: 1.348277ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:36:29Z"
    - latency: 1.225515ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:41:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-85-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-85.us-west-1.compute.internal
      uid: 6fd57672-a7f8-4e06-b40d-89a2333677be
    resourceVersion: "107617"
    uid: 62e39aa9-2944-4e26-b66a-098c20e419d4
  spec:
    sourcePod: network-check-source-6f78d59f99-gqbfm
    targetEndpoint: a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:47:29Z"
      message: 'load-balancer-api-external: tcp connection to a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.205116ms
      message: 'load-balancer-api-external: tcp connection to a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:47:29Z"
    - latency: 10.930869ms
      message: 'load-balancer-api-external: resolved host name a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:47:29Z"
    - latency: 52.6388ms
      message: 'load-balancer-api-external: tcp connection to a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:46:29Z"
    - latency: 6.982056ms
      message: 'load-balancer-api-external: resolved host name a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:46:29Z"
    - latency: 53.962114ms
      message: 'load-balancer-api-external: tcp connection to a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:45:29Z"
    - latency: 6.688459ms
      message: 'load-balancer-api-external: resolved host name a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:45:29Z"
    - latency: 57.574258ms
      message: 'load-balancer-api-external: tcp connection to a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 67.276969ms
      message: 'load-balancer-api-external: resolved host name a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 54.239298ms
      message: 'load-balancer-api-external: tcp connection to a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 6.028293ms
      message: 'load-balancer-api-external: resolved host name a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:43:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:41:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-85-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-85.us-west-1.compute.internal
      uid: 6fd57672-a7f8-4e06-b40d-89a2333677be
    resourceVersion: "107616"
    uid: c7ce6270-db96-4112-af76-722efebcba5f
  spec:
    sourcePod: network-check-source-6f78d59f99-gqbfm
    targetEndpoint: a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:47:29Z"
      message: 'load-balancer-api-internal: tcp connection to a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 53.264635ms
      message: 'load-balancer-api-internal: tcp connection to a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:47:29Z"
    - latency: 10.932664ms
      message: 'load-balancer-api-internal: resolved host name a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:47:29Z"
    - latency: 52.650653ms
      message: 'load-balancer-api-internal: tcp connection to a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:46:29Z"
    - latency: 7.04513ms
      message: 'load-balancer-api-internal: resolved host name a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:46:29Z"
    - latency: 53.928306ms
      message: 'load-balancer-api-internal: tcp connection to a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:45:29Z"
    - latency: 6.796631ms
      message: 'load-balancer-api-internal: resolved host name a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:45:29Z"
    - latency: 54.380084ms
      message: 'load-balancer-api-internal: tcp connection to a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 67.335668ms
      message: 'load-balancer-api-internal: resolved host name a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 53.411204ms
      message: 'load-balancer-api-internal: tcp connection to a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 6.114538ms
      message: 'load-balancer-api-internal: resolved host name a3138b275a5484ea19a8d9971322f756-b97bd68a7b677e68.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:43:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:41:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-85-to-network-check-target-ip-10-0-128-165
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-85.us-west-1.compute.internal
      uid: 6fd57672-a7f8-4e06-b40d-89a2333677be
    resourceVersion: "105103"
    uid: bb1b5053-4aab-4f06-966b-daa6e52eb629
  spec:
    sourcePod: network-check-source-6f78d59f99-gqbfm
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:48:29Z"
      message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.412815ms
      message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 1.870298ms
      message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 1.730729ms
      message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:29Z"
    - latency: 2.326697ms
      message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:29Z"
    - latency: 1.861121ms
      message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:29Z"
    - latency: 2.465268ms
      message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:29Z"
    - latency: 2.054558ms
      message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:38:29Z"
    - latency: 2.275764ms
      message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:37:29Z"
    - latency: 2.214532ms
      message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:36:29Z"
    - latency: 1.943574ms
      message: 'network-check-target-ip-10-0-128-165: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:41:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-85-to-network-check-target-ip-10-0-138-149
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-85.us-west-1.compute.internal
      uid: 6fd57672-a7f8-4e06-b40d-89a2333677be
    resourceVersion: "105102"
    uid: 00146259-0f72-47f4-bb47-38a215f73a61
  spec:
    sourcePod: network-check-source-6f78d59f99-gqbfm
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:48:29Z"
      message: 'network-check-target-ip-10-0-138-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.466825ms
      message: 'network-check-target-ip-10-0-138-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 2.490616ms
      message: 'network-check-target-ip-10-0-138-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 2.375487ms
      message: 'network-check-target-ip-10-0-138-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:29Z"
    - latency: 2.384143ms
      message: 'network-check-target-ip-10-0-138-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:29Z"
    - latency: 2.175856ms
      message: 'network-check-target-ip-10-0-138-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:29Z"
    - latency: 2.810147ms
      message: 'network-check-target-ip-10-0-138-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:29Z"
    - latency: 2.034547ms
      message: 'network-check-target-ip-10-0-138-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:38:29Z"
    - latency: 2.186451ms
      message: 'network-check-target-ip-10-0-138-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:37:29Z"
    - latency: 2.219691ms
      message: 'network-check-target-ip-10-0-138-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:36:29Z"
    - latency: 2.33906ms
      message: 'network-check-target-ip-10-0-138-149: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:41:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-85-to-network-check-target-ip-10-0-138-85
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-85.us-west-1.compute.internal
      uid: 6fd57672-a7f8-4e06-b40d-89a2333677be
    resourceVersion: "105101"
    uid: a486149b-89f4-4c08-959d-45d6464500b4
  spec:
    sourcePod: network-check-source-6f78d59f99-gqbfm
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:48:29Z"
      message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.243377ms
      message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 1.525572ms
      message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 1.062409ms
      message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:42:29Z"
    - latency: 1.364538ms
      message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:41:29Z"
    - latency: 975.139µs
      message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:40:29Z"
    - latency: 1.008033ms
      message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:39:29Z"
    - latency: 895.485µs
      message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:38:29Z"
    - latency: 912.776µs
      message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:37:29Z"
    - latency: 915.588µs
      message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:36:29Z"
    - latency: 1.481016ms
      message: 'network-check-target-ip-10-0-138-85: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:35:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-30T20:41:28Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-85-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-85.us-west-1.compute.internal
      uid: 6fd57672-a7f8-4e06-b40d-89a2333677be
    resourceVersion: "107615"
    uid: 8b5faff3-46f9-492b-bcde-fac5e1349560
  spec:
    sourcePod: network-check-source-6f78d59f99-gqbfm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-30T20:47:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.117824ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:47:29Z"
    - latency: 1.805565ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:47:29Z"
    - latency: 904.902µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:46:29Z"
    - latency: 2.174901ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:46:29Z"
    - latency: 964.499µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:45:29Z"
    - latency: 1.875264ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:45:29Z"
    - latency: 2.795973ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 3.554098ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:44:29Z"
    - latency: 1.040047ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-30T21:43:29Z"
    - latency: 1.872777ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-30T21:43:29Z"
kind: List
metadata:
  resourceVersion: ""