apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T20:03:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-10-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-10.ec2.internal
      uid: 0f01575a-88af-49e7-a57d-151852aaaa4e
    resourceVersion: "32433"
    uid: 8b86bf79-434c-43cb-8928-4dc9cf3a8b48
  spec:
    sourcePod: network-check-source-8894fc9bd-vrwhw
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T20:10:32Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.117929ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:45:32Z"
    - latency: 1.292055ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:44:32Z"
    - latency: 1.034465ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:43:32Z"
    - latency: 917.867µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:42:32Z"
    - latency: 1.150146ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:41:32Z"
    - latency: 1.066486ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:40:32Z"
    - latency: 1.353972ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:39:32Z"
    - latency: 797.818µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:38:32Z"
    - latency: 955.981µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:37:32Z"
    - latency: 1.104921ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:36:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T20:03:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-10-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-10.ec2.internal
      uid: 0f01575a-88af-49e7-a57d-151852aaaa4e
    resourceVersion: "32434"
    uid: 7c1ff9c0-d754-4554-b94a-9a4d1c63e47b
  spec:
    sourcePod: network-check-source-8894fc9bd-vrwhw
    targetEndpoint: a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T20:09:32Z"
      message: 'load-balancer-api-external: tcp connection to a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.304885ms
      message: 'load-balancer-api-external: tcp connection to a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:45:32Z"
    - latency: 6.953874ms
      message: 'load-balancer-api-external: resolved host name a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:45:32Z"
    - latency: 6.23783ms
      message: 'load-balancer-api-external: tcp connection to a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:44:32Z"
    - latency: 6.310239ms
      message: 'load-balancer-api-external: resolved host name a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:44:32Z"
    - latency: 5.714513ms
      message: 'load-balancer-api-external: tcp connection to a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:43:32Z"
    - latency: 6.820362ms
      message: 'load-balancer-api-external: resolved host name a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:43:32Z"
    - latency: 4.469814ms
      message: 'load-balancer-api-external: tcp connection to a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:42:32Z"
    - latency: 6.039328ms
      message: 'load-balancer-api-external: resolved host name a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:42:32Z"
    - latency: 5.344278ms
      message: 'load-balancer-api-external: tcp connection to a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:41:32Z"
    - latency: 6.578021ms
      message: 'load-balancer-api-external: resolved host name a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:41:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T20:03:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-10-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-10.ec2.internal
      uid: 0f01575a-88af-49e7-a57d-151852aaaa4e
    resourceVersion: "32435"
    uid: 62e4fdc2-795a-4a36-9d84-ad82258d8260
  spec:
    sourcePod: network-check-source-8894fc9bd-vrwhw
    targetEndpoint: a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T20:09:32Z"
      message: 'load-balancer-api-internal: tcp connection to a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.333547ms
      message: 'load-balancer-api-internal: tcp connection to a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:45:32Z"
    - latency: 6.944735ms
      message: 'load-balancer-api-internal: resolved host name a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:45:32Z"
    - latency: 4.294119ms
      message: 'load-balancer-api-internal: tcp connection to a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:44:32Z"
    - latency: 6.393138ms
      message: 'load-balancer-api-internal: resolved host name a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:44:32Z"
    - latency: 5.683441ms
      message: 'load-balancer-api-internal: tcp connection to a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:43:32Z"
    - latency: 6.843279ms
      message: 'load-balancer-api-internal: resolved host name a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:43:32Z"
    - latency: 4.433135ms
      message: 'load-balancer-api-internal: tcp connection to a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:42:32Z"
    - latency: 6.069063ms
      message: 'load-balancer-api-internal: resolved host name a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:42:32Z"
    - latency: 5.34652ms
      message: 'load-balancer-api-internal: tcp connection to a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:41:32Z"
    - latency: 6.613862ms
      message: 'load-balancer-api-internal: resolved host name a9dec4159b4814b57834c6beaf7d6d6b-b5b650658a61b346.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:41:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T20:03:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-10-to-network-check-target-ip-10-0-128-160
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-10.ec2.internal
      uid: 0f01575a-88af-49e7-a57d-151852aaaa4e
    resourceVersion: "32431"
    uid: 5d8bd69d-716b-4f7c-9bc7-da18b4fe98cb
  spec:
    sourcePod: network-check-source-8894fc9bd-vrwhw
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T20:10:32Z"
      message: 'network-check-target-ip-10-0-128-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.011131ms
      message: 'network-check-target-ip-10-0-128-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:45:32Z"
    - latency: 2.100953ms
      message: 'network-check-target-ip-10-0-128-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:44:32Z"
    - latency: 2.219178ms
      message: 'network-check-target-ip-10-0-128-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:43:32Z"
    - latency: 2.204302ms
      message: 'network-check-target-ip-10-0-128-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:42:32Z"
    - latency: 2.196629ms
      message: 'network-check-target-ip-10-0-128-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:41:32Z"
    - latency: 2.009866ms
      message: 'network-check-target-ip-10-0-128-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:40:32Z"
    - latency: 1.967138ms
      message: 'network-check-target-ip-10-0-128-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:39:32Z"
    - latency: 2.16928ms
      message: 'network-check-target-ip-10-0-128-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:38:32Z"
    - latency: 2.370591ms
      message: 'network-check-target-ip-10-0-128-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:37:32Z"
    - latency: 2.170901ms
      message: 'network-check-target-ip-10-0-128-160: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:36:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T20:03:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-10-to-network-check-target-ip-10-0-135-215
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-10.ec2.internal
      uid: 0f01575a-88af-49e7-a57d-151852aaaa4e
    resourceVersion: "32430"
    uid: c3fb7f03-4d6e-4d85-8946-8fe90082fc7d
  spec:
    sourcePod: network-check-source-8894fc9bd-vrwhw
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T20:10:32Z"
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.71035ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:45:32Z"
    - latency: 1.611728ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:44:32Z"
    - latency: 1.738615ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:43:32Z"
    - latency: 1.834447ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:42:32Z"
    - latency: 1.585592ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:41:32Z"
    - latency: 1.621147ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:40:32Z"
    - latency: 1.535119ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:39:32Z"
    - latency: 1.728622ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:38:32Z"
    - latency: 1.535232ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:37:32Z"
    - latency: 1.804064ms
      message: 'network-check-target-ip-10-0-135-215: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:36:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T20:03:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-10-to-network-check-target-ip-10-0-139-10
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-10.ec2.internal
      uid: 0f01575a-88af-49e7-a57d-151852aaaa4e
    resourceVersion: "32429"
    uid: cf445c66-40ad-4b86-9378-75ca26faccab
  spec:
    sourcePod: network-check-source-8894fc9bd-vrwhw
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T20:10:32Z"
      message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 860.656µs
      message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:45:32Z"
    - latency: 1.507357ms
      message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:44:32Z"
    - latency: 831.397µs
      message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:43:32Z"
    - latency: 850.054µs
      message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:42:32Z"
    - latency: 1.199617ms
      message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:41:32Z"
    - latency: 872.108µs
      message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:40:32Z"
    - latency: 1.06414ms
      message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:39:32Z"
    - latency: 1.481012ms
      message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:38:32Z"
    - latency: 743.352µs
      message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:37:32Z"
    - latency: 884.929µs
      message: 'network-check-target-ip-10-0-139-10: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:36:32Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-04-22T20:03:31Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-10-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-10.ec2.internal
      uid: 0f01575a-88af-49e7-a57d-151852aaaa4e
    resourceVersion: "32432"
    uid: a7cd9153-6588-48be-b604-8db0327eb22b
  spec:
    sourcePod: network-check-source-8894fc9bd-vrwhw
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-04-22T20:09:32Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 860.61µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:45:32Z"
    - latency: 2.03957ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:45:32Z"
    - latency: 717.327µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:44:32Z"
    - latency: 1.633086ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:44:32Z"
    - latency: 835.978µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:43:32Z"
    - latency: 1.677726ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:43:32Z"
    - latency: 706.851µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:42:32Z"
    - latency: 1.646365ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:42:32Z"
    - latency: 1.005814ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-04-22T20:41:32Z"
    - latency: 1.698651ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-04-22T20:41:32Z"
kind: List
metadata:
  resourceVersion: ""