apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:08:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-117-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-117.ec2.internal
      uid: 23711b19-a411-4db9-83a9-733fabd981ec
    resourceVersion: "54906"
    uid: c6ad3fbf-3d57-46c1-9cf7-aa6cb802242d
  spec:
    sourcePod: network-check-source-989f8b8dc-62svf
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:15:48Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.142886ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 1.128417ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 982.188µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:48Z"
    - latency: 1.137403ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:48Z"
    - latency: 1.125483ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:39:48Z"
    - latency: 1.152887ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:38:48Z"
    - latency: 1.211657ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:37:48Z"
    - latency: 1.438735ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:36:48Z"
    - latency: 1.179206ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:35:48Z"
    - latency: 798.251µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:08:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-117-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-117.ec2.internal
      uid: 23711b19-a411-4db9-83a9-733fabd981ec
    resourceVersion: "55856"
    uid: 464548e0-4317-45f5-b684-2bf6a15662c9
  spec:
    sourcePod: network-check-source-989f8b8dc-62svf
    targetEndpoint: a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:14:48Z"
      message: 'load-balancer-api-external: tcp connection to a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.845996ms
      message: 'load-balancer-api-external: tcp connection to a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 8.188576ms
      message: 'load-balancer-api-external: resolved host name a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 5.682383ms
      message: 'load-balancer-api-external: tcp connection to a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 7.681073ms
      message: 'load-balancer-api-external: resolved host name a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 4.232225ms
      message: 'load-balancer-api-external: tcp connection to a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 8.179647ms
      message: 'load-balancer-api-external: resolved host name a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 4.733093ms
      message: 'load-balancer-api-external: tcp connection to a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:48Z"
    - latency: 9.32021ms
      message: 'load-balancer-api-external: resolved host name a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:41:48Z"
    - latency: 3.659514ms
      message: 'load-balancer-api-external: tcp connection to a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:48Z"
    - latency: 8.738858ms
      message: 'load-balancer-api-external: resolved host name a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:40:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:08:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-117-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-117.ec2.internal
      uid: 23711b19-a411-4db9-83a9-733fabd981ec
    resourceVersion: "55855"
    uid: dd88c463-e882-433b-bdb0-b23a0c0f4bc9
  spec:
    sourcePod: network-check-source-989f8b8dc-62svf
    targetEndpoint: a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:14:48Z"
      message: 'load-balancer-api-internal: tcp connection to a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.946132ms
      message: 'load-balancer-api-internal: tcp connection to a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 8.205081ms
      message: 'load-balancer-api-internal: resolved host name a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 5.702951ms
      message: 'load-balancer-api-internal: tcp connection to a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 7.62046ms
      message: 'load-balancer-api-internal: resolved host name a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 4.821834ms
      message: 'load-balancer-api-internal: tcp connection to a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 8.255088ms
      message: 'load-balancer-api-internal: resolved host name a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 4.78606ms
      message: 'load-balancer-api-internal: tcp connection to a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:48Z"
    - latency: 9.38781ms
      message: 'load-balancer-api-internal: resolved host name a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:41:48Z"
    - latency: 4.232412ms
      message: 'load-balancer-api-internal: tcp connection to a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:48Z"
    - latency: 8.655107ms
      message: 'load-balancer-api-internal: resolved host name a305e46cef15a4cdf9d85d128f7ae7c5-fa682c1f4b87f73b.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:40:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:08:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-117-to-network-check-target-ip-10-0-131-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-117.ec2.internal
      uid: 23711b19-a411-4db9-83a9-733fabd981ec
    resourceVersion: "54905"
    uid: 9d34b1b7-19cb-46ef-a64e-fb8020788060
  spec:
    sourcePod: network-check-source-989f8b8dc-62svf
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:15:48Z"
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.245307ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 2.201359ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 2.621616ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:48Z"
    - latency: 2.309929ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:48Z"
    - latency: 2.058617ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:39:48Z"
    - latency: 2.204117ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:38:48Z"
    - latency: 2.317128ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:37:48Z"
    - latency: 2.370647ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:36:48Z"
    - latency: 2.134679ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:35:48Z"
    - latency: 2.136861ms
      message: 'network-check-target-ip-10-0-131-1: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:08:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-117-to-network-check-target-ip-10-0-133-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-117.ec2.internal
      uid: 23711b19-a411-4db9-83a9-733fabd981ec
    resourceVersion: "54903"
    uid: 0d92cf8d-48c0-4d5c-90b3-98c865c6903a
  spec:
    sourcePod: network-check-source-989f8b8dc-62svf
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:15:48Z"
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 956.573µs
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 963.861µs
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 919.534µs
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:48Z"
    - latency: 1.566076ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:48Z"
    - latency: 785.872µs
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:39:48Z"
    - latency: 949.785µs
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:38:48Z"
    - latency: 1.368786ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:37:48Z"
    - latency: 1.197993ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:36:48Z"
    - latency: 862.371µs
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:35:48Z"
    - latency: 818.94µs
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:08:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-117-to-network-check-target-ip-10-0-141-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-117.ec2.internal
      uid: 23711b19-a411-4db9-83a9-733fabd981ec
    resourceVersion: "54904"
    uid: d6087ef9-6764-44f4-998f-21a4347f3cf1
  spec:
    sourcePod: network-check-source-989f8b8dc-62svf
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:15:48Z"
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.17783ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 1.984986ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 2.620782ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:48Z"
    - latency: 1.910665ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:48Z"
    - latency: 1.874779ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:39:48Z"
    - latency: 1.915334ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:38:48Z"
    - latency: 1.749704ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:37:48Z"
    - latency: 2.314212ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:36:48Z"
    - latency: 2.126585ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:35:48Z"
    - latency: 1.450809ms
      message: 'network-check-target-ip-10-0-141-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:34:48Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-06T19:08:47Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-117-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-117.ec2.internal
      uid: 23711b19-a411-4db9-83a9-733fabd981ec
    resourceVersion: "55854"
    uid: 861f469b-6b9f-4a65-97b5-ae1582ff08ad
  spec:
    sourcePod: network-check-source-989f8b8dc-62svf
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-06T19:14:48Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 940.731µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 1.820926ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:44:48Z"
    - latency: 1.098055ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 1.64456ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:43:48Z"
    - latency: 780.157µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 1.667396ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:42:48Z"
    - latency: 825.843µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:41:48Z"
    - latency: 2.637075ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:41:48Z"
    - latency: 1.126026ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-06T19:40:48Z"
    - latency: 1.84236ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-06T19:40:48Z"
kind: List
metadata:
  resourceVersion: ""