apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:32:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-222-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-222.us-east-2.compute.internal
      uid: 69a7780e-3624-4aa2-b536-3a866e5cd6c9
    resourceVersion: "144315"
    uid: 5fbceb94-50e2-4671-9ea0-3c8ef2f2050d
  spec:
    sourcePod: network-check-source-6f78d59f99-cbhrt
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:39:59Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 979.73µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:21:59Z"
    - latency: 1.310129ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:20:59Z"
    - latency: 1.523023ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:19:59Z"
    - latency: 912.062µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:18:59Z"
    - latency: 1.649621ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:17:59Z"
    - latency: 837.523µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:59Z"
    - latency: 918.713µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:59Z"
    - latency: 1.188337ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:59Z"
    - latency: 1.279366ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:59Z"
    - latency: 1.309997ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:32:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-222-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-222.us-east-2.compute.internal
      uid: 69a7780e-3624-4aa2-b536-3a866e5cd6c9
    resourceVersion: "142064"
    uid: 37241b22-5b20-4e91-ba9c-f4a005c2765a
  spec:
    sourcePod: network-check-source-6f78d59f99-cbhrt
    targetEndpoint: a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:38:59Z"
      message: 'load-balancer-api-external: tcp connection to a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.404195ms
      message: 'load-balancer-api-external: tcp connection to a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:20:59Z"
    - latency: 6.333359ms
      message: 'load-balancer-api-external: resolved host name a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:20:59Z"
    - latency: 5.450848ms
      message: 'load-balancer-api-external: tcp connection to a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:19:59Z"
    - latency: 7.221142ms
      message: 'load-balancer-api-external: resolved host name a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:19:59Z"
    - latency: 7.011858ms
      message: 'load-balancer-api-external: tcp connection to a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:18:59Z"
    - latency: 6.513851ms
      message: 'load-balancer-api-external: resolved host name a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:18:59Z"
    - latency: 7.175909ms
      message: 'load-balancer-api-external: tcp connection to a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:17:59Z"
    - latency: 7.221973ms
      message: 'load-balancer-api-external: resolved host name a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:17:59Z"
    - latency: 4.98776ms
      message: 'load-balancer-api-external: tcp connection to a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:59Z"
    - latency: 6.465272ms
      message: 'load-balancer-api-external: resolved host name a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:16:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:32:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-222-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-222.us-east-2.compute.internal
      uid: 69a7780e-3624-4aa2-b536-3a866e5cd6c9
    resourceVersion: "142065"
    uid: 0ee2e7d4-21bb-465a-a234-071fdd11792c
  spec:
    sourcePod: network-check-source-6f78d59f99-cbhrt
    targetEndpoint: a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:38:59Z"
      message: 'load-balancer-api-internal: tcp connection to a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.415612ms
      message: 'load-balancer-api-internal: tcp connection to a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:20:59Z"
    - latency: 6.204214ms
      message: 'load-balancer-api-internal: resolved host name a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:20:59Z"
    - latency: 5.462365ms
      message: 'load-balancer-api-internal: tcp connection to a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:19:59Z"
    - latency: 7.167078ms
      message: 'load-balancer-api-internal: resolved host name a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:19:59Z"
    - latency: 6.966203ms
      message: 'load-balancer-api-internal: tcp connection to a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:18:59Z"
    - latency: 6.492902ms
      message: 'load-balancer-api-internal: resolved host name a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:18:59Z"
    - latency: 7.211138ms
      message: 'load-balancer-api-internal: tcp connection to a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:17:59Z"
    - latency: 7.126182ms
      message: 'load-balancer-api-internal: resolved host name a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:17:59Z"
    - latency: 5.024623ms
      message: 'load-balancer-api-internal: tcp connection to a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:59Z"
    - latency: 6.389272ms
      message: 'load-balancer-api-internal: resolved host name a7725fdb8ab6242a9842c621ab8c0953-14e5e7b965086969.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:16:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:32:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-222-to-network-check-target-ip-10-0-131-234
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-222.us-east-2.compute.internal
      uid: 69a7780e-3624-4aa2-b536-3a866e5cd6c9
    resourceVersion: "144313"
    uid: 0e394fd6-5104-4791-9d57-a197231784f0
  spec:
    sourcePod: network-check-source-6f78d59f99-cbhrt
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:39:59Z"
      message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.158938ms
      message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:21:59Z"
    - latency: 2.190082ms
      message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:20:59Z"
    - latency: 2.393938ms
      message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:19:59Z"
    - latency: 2.183678ms
      message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:18:59Z"
    - latency: 2.60223ms
      message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:17:59Z"
    - latency: 2.460291ms
      message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:59Z"
    - latency: 2.044825ms
      message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:59Z"
    - latency: 2.348397ms
      message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:59Z"
    - latency: 2.403556ms
      message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:59Z"
    - latency: 2.183336ms
      message: 'network-check-target-ip-10-0-131-234: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:32:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-222-to-network-check-target-ip-10-0-133-204
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-222.us-east-2.compute.internal
      uid: 69a7780e-3624-4aa2-b536-3a866e5cd6c9
    resourceVersion: "144314"
    uid: 32a51374-3b5a-4769-8b46-e6514243831a
  spec:
    sourcePod: network-check-source-6f78d59f99-cbhrt
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:39:59Z"
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.137769ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:21:59Z"
    - latency: 1.916496ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:20:59Z"
    - latency: 1.980146ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:19:59Z"
    - latency: 2.262529ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:18:59Z"
    - latency: 2.15793ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:17:59Z"
    - latency: 1.999701ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:59Z"
    - latency: 1.878009ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:59Z"
    - latency: 2.033656ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:59Z"
    - latency: 2.216924ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:59Z"
    - latency: 1.83216ms
      message: 'network-check-target-ip-10-0-133-204: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:32:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-222-to-network-check-target-ip-10-0-134-222
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-222.us-east-2.compute.internal
      uid: 69a7780e-3624-4aa2-b536-3a866e5cd6c9
    resourceVersion: "144312"
    uid: fcf7c01c-d56f-4a08-a375-0e41363eb1cb
  spec:
    sourcePod: network-check-source-6f78d59f99-cbhrt
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:39:59Z"
      message: 'network-check-target-ip-10-0-134-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 980.107µs
      message: 'network-check-target-ip-10-0-134-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:21:59Z"
    - latency: 932.042µs
      message: 'network-check-target-ip-10-0-134-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:20:59Z"
    - latency: 1.216318ms
      message: 'network-check-target-ip-10-0-134-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:19:59Z"
    - latency: 1.113318ms
      message: 'network-check-target-ip-10-0-134-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:18:59Z"
    - latency: 957.222µs
      message: 'network-check-target-ip-10-0-134-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:17:59Z"
    - latency: 1.087399ms
      message: 'network-check-target-ip-10-0-134-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:59Z"
    - latency: 1.054534ms
      message: 'network-check-target-ip-10-0-134-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:15:59Z"
    - latency: 1.153088ms
      message: 'network-check-target-ip-10-0-134-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:14:59Z"
    - latency: 1.054242ms
      message: 'network-check-target-ip-10-0-134-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:13:59Z"
    - latency: 1.233557ms
      message: 'network-check-target-ip-10-0-134-222: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:12:59Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T19:32:58Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-222-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-222.us-east-2.compute.internal
      uid: 69a7780e-3624-4aa2-b536-3a866e5cd6c9
    resourceVersion: "142063"
    uid: 94ff130c-3626-479c-86e8-5f6ce5b2adea
  spec:
    sourcePod: network-check-source-6f78d59f99-cbhrt
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T19:38:59Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.011044ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:20:59Z"
    - latency: 1.842621ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:20:59Z"
    - latency: 1.232851ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:19:59Z"
    - latency: 1.919627ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:19:59Z"
    - latency: 928.051µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:18:59Z"
    - latency: 1.978826ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:18:59Z"
    - latency: 961µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:17:59Z"
    - latency: 1.899913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:17:59Z"
    - latency: 792.984µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T20:16:59Z"
    - latency: 1.759801ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T20:16:59Z"
kind: List
metadata:
  resourceVersion: ""