apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T15:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-69-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-69.ec2.internal
      uid: b9b21f25-5dd8-44e2-b623-1adb0363462a
    resourceVersion: "53947"
    uid: f3faba5b-5898-4512-b5c8-bff6805090a2
  spec:
    sourcePod: network-check-source-869dcfcdcd-fjmnl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T16:05:30Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.148226ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:33:30Z"
    - latency: 1.277261ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:32:30Z"
    - latency: 1.104928ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:31:30Z"
    - latency: 1.112611ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:30:30Z"
    - latency: 1.401817ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:29:30Z"
    - latency: 1.349594ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:28:30Z"
    - latency: 1.54827ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:27:30Z"
    - latency: 1.090534ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:26:30Z"
    - latency: 1.229088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:25:30Z"
    - latency: 1.104887ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:24:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T15:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-69-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-69.ec2.internal
      uid: b9b21f25-5dd8-44e2-b623-1adb0363462a
    resourceVersion: "54817"
    uid: 5e270107-ec3d-4df9-b1d9-17ff4c1a44b7
  spec:
    sourcePod: network-check-source-869dcfcdcd-fjmnl
    targetEndpoint: a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T16:04:30Z"
      message: 'load-balancer-api-external: tcp connection to a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.613728ms
      message: 'load-balancer-api-external: tcp connection to a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:34:30Z"
    - latency: 6.477353ms
      message: 'load-balancer-api-external: resolved host name a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:34:30Z"
    - latency: 5.323752ms
      message: 'load-balancer-api-external: tcp connection to a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:33:30Z"
    - latency: 7.222891ms
      message: 'load-balancer-api-external: resolved host name a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:33:30Z"
    - latency: 4.339133ms
      message: 'load-balancer-api-external: tcp connection to a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:32:30Z"
    - latency: 7.034179ms
      message: 'load-balancer-api-external: resolved host name a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:32:30Z"
    - latency: 5.74054ms
      message: 'load-balancer-api-external: tcp connection to a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:31:30Z"
    - latency: 9.872959ms
      message: 'load-balancer-api-external: resolved host name a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:31:30Z"
    - latency: 4.541399ms
      message: 'load-balancer-api-external: tcp connection to a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:30:30Z"
    - latency: 6.967088ms
      message: 'load-balancer-api-external: resolved host name a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:30:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T15:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-69-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-69.ec2.internal
      uid: b9b21f25-5dd8-44e2-b623-1adb0363462a
    resourceVersion: "54816"
    uid: 880392ad-2e7b-4caa-b375-dd437dc16dea
  spec:
    sourcePod: network-check-source-869dcfcdcd-fjmnl
    targetEndpoint: a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T16:04:30Z"
      message: 'load-balancer-api-internal: tcp connection to a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.596973ms
      message: 'load-balancer-api-internal: tcp connection to a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:34:30Z"
    - latency: 6.550754ms
      message: 'load-balancer-api-internal: resolved host name a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:34:30Z"
    - latency: 5.309153ms
      message: 'load-balancer-api-internal: tcp connection to a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:33:30Z"
    - latency: 7.286225ms
      message: 'load-balancer-api-internal: resolved host name a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:33:30Z"
    - latency: 4.360985ms
      message: 'load-balancer-api-internal: tcp connection to a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:32:30Z"
    - latency: 7.103428ms
      message: 'load-balancer-api-internal: resolved host name a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:32:30Z"
    - latency: 4.165675ms
      message: 'load-balancer-api-internal: tcp connection to a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:31:30Z"
    - latency: 9.925538ms
      message: 'load-balancer-api-internal: resolved host name a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:31:30Z"
    - latency: 4.582116ms
      message: 'load-balancer-api-internal: tcp connection to a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:30:30Z"
    - latency: 6.802694ms
      message: 'load-balancer-api-internal: resolved host name a96ec2195720045ca991b249aae06822-eecf3d8f73a27b61.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:30:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T15:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-69-to-network-check-target-ip-10-0-135-156
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-69.ec2.internal
      uid: b9b21f25-5dd8-44e2-b623-1adb0363462a
    resourceVersion: "53944"
    uid: 1c104dfe-add9-4c0b-b450-95c1d7681882
  spec:
    sourcePod: network-check-source-869dcfcdcd-fjmnl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T16:05:30Z"
      message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.562332ms
      message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:33:30Z"
    - latency: 1.69067ms
      message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:32:30Z"
    - latency: 2.020059ms
      message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:31:30Z"
    - latency: 2.053935ms
      message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:30:30Z"
    - latency: 1.777248ms
      message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:29:30Z"
    - latency: 1.675042ms
      message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:28:30Z"
    - latency: 1.798864ms
      message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:27:30Z"
    - latency: 1.881189ms
      message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:26:30Z"
    - latency: 1.994026ms
      message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:25:30Z"
    - latency: 2.004749ms
      message: 'network-check-target-ip-10-0-135-156: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:24:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T15:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-69-to-network-check-target-ip-10-0-136-164
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-69.ec2.internal
      uid: b9b21f25-5dd8-44e2-b623-1adb0363462a
    resourceVersion: "53946"
    uid: 2d03fbb2-ce52-4723-b702-117b515b6316
  spec:
    sourcePod: network-check-source-869dcfcdcd-fjmnl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T16:05:30Z"
      message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.497525ms
      message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:33:30Z"
    - latency: 2.258078ms
      message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:32:30Z"
    - latency: 2.375297ms
      message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:31:30Z"
    - latency: 2.537391ms
      message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:30:30Z"
    - latency: 2.14643ms
      message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:29:30Z"
    - latency: 2.187991ms
      message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:28:30Z"
    - latency: 2.234544ms
      message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:27:30Z"
    - latency: 2.335495ms
      message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:26:30Z"
    - latency: 2.31634ms
      message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:25:30Z"
    - latency: 2.305037ms
      message: 'network-check-target-ip-10-0-136-164: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:24:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T15:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-69-to-network-check-target-ip-10-0-139-69
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-69.ec2.internal
      uid: b9b21f25-5dd8-44e2-b623-1adb0363462a
    resourceVersion: "53945"
    uid: d8f9b66c-21b2-477c-9d1d-6ef86a282290
  spec:
    sourcePod: network-check-source-869dcfcdcd-fjmnl
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T16:05:30Z"
      message: 'network-check-target-ip-10-0-139-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.373157ms
      message: 'network-check-target-ip-10-0-139-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:33:30Z"
    - latency: 1.144111ms
      message: 'network-check-target-ip-10-0-139-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:32:30Z"
    - latency: 1.039898ms
      message: 'network-check-target-ip-10-0-139-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:31:30Z"
    - latency: 1.819438ms
      message: 'network-check-target-ip-10-0-139-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:30:30Z"
    - latency: 1.213376ms
      message: 'network-check-target-ip-10-0-139-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:29:30Z"
    - latency: 1.134696ms
      message: 'network-check-target-ip-10-0-139-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:28:30Z"
    - latency: 1.203138ms
      message: 'network-check-target-ip-10-0-139-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:27:30Z"
    - latency: 1.503517ms
      message: 'network-check-target-ip-10-0-139-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:26:30Z"
    - latency: 914.333µs
      message: 'network-check-target-ip-10-0-139-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:25:30Z"
    - latency: 1.283784ms
      message: 'network-check-target-ip-10-0-139-69: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:24:30Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T15:58:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-69-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-69.ec2.internal
      uid: b9b21f25-5dd8-44e2-b623-1adb0363462a
    resourceVersion: "54815"
    uid: f31f61dd-fc72-4234-944e-3f3c6599b76c
  spec:
    sourcePod: network-check-source-869dcfcdcd-fjmnl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T16:04:30Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.286468ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:34:30Z"
    - latency: 1.800986ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:34:30Z"
    - latency: 904.641µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:33:30Z"
    - latency: 2.033704ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:33:30Z"
    - latency: 873.925µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:32:30Z"
    - latency: 1.74771ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:32:30Z"
    - latency: 1.065602ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:31:30Z"
    - latency: 1.722635ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:31:30Z"
    - latency: 846.691µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T16:30:30Z"
    - latency: 2.264583ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T16:30:30Z"
kind: List
metadata:
  resourceVersion: ""