apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:49:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-249-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-249.ec2.internal
      uid: e39f722b-a106-45ee-97e1-4a407053010d
    resourceVersion: "54756"
    uid: f0df4c26-f206-4dc7-958c-57fd504ebe55
  spec:
    sourcePod: network-check-source-869dcfcdcd-d9ldz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:56:43Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.072179ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:43Z"
    - latency: 1.150711ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:43Z"
    - latency: 1.131993ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:43Z"
    - latency: 917.283µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:21:43Z"
    - latency: 1.030723ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:20:43Z"
    - latency: 1.441205ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:19:43Z"
    - latency: 1.090077ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:18:43Z"
    - latency: 1.123277ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:43Z"
    - latency: 1.323651ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:43Z"
    - latency: 1.087283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:15:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:49:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-249-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-249.ec2.internal
      uid: e39f722b-a106-45ee-97e1-4a407053010d
    resourceVersion: "55736"
    uid: 46d8a684-68ae-486d-b376-662673593aee
  spec:
    sourcePod: network-check-source-869dcfcdcd-d9ldz
    targetEndpoint: a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:55:43Z"
      message: 'load-balancer-api-external: tcp connection to a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.065132ms
      message: 'load-balancer-api-external: tcp connection to a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:25:43Z"
    - latency: 6.976986ms
      message: 'load-balancer-api-external: resolved host name a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:25:43Z"
    - latency: 6.174085ms
      message: 'load-balancer-api-external: tcp connection to a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:43Z"
    - latency: 8.267142ms
      message: 'load-balancer-api-external: resolved host name a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:24:43Z"
    - latency: 6.271341ms
      message: 'load-balancer-api-external: tcp connection to a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:43Z"
    - latency: 6.522762ms
      message: 'load-balancer-api-external: resolved host name a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:23:43Z"
    - latency: 6.055475ms
      message: 'load-balancer-api-external: tcp connection to a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:43Z"
    - latency: 6.385185ms
      message: 'load-balancer-api-external: resolved host name a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:22:43Z"
    - latency: 4.750809ms
      message: 'load-balancer-api-external: tcp connection to a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:21:43Z"
    - latency: 5.931068ms
      message: 'load-balancer-api-external: resolved host name a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:21:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:49:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-249-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-249.ec2.internal
      uid: e39f722b-a106-45ee-97e1-4a407053010d
    resourceVersion: "55737"
    uid: f6109fa4-908c-41eb-a666-d4cc723d5a6a
  spec:
    sourcePod: network-check-source-869dcfcdcd-d9ldz
    targetEndpoint: a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:55:43Z"
      message: 'load-balancer-api-internal: tcp connection to a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.098743ms
      message: 'load-balancer-api-internal: tcp connection to a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:25:43Z"
    - latency: 7.033657ms
      message: 'load-balancer-api-internal: resolved host name a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:25:43Z"
    - latency: 6.256455ms
      message: 'load-balancer-api-internal: tcp connection to a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:43Z"
    - latency: 8.245912ms
      message: 'load-balancer-api-internal: resolved host name a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:24:43Z"
    - latency: 6.164936ms
      message: 'load-balancer-api-internal: tcp connection to a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:43Z"
    - latency: 6.562166ms
      message: 'load-balancer-api-internal: resolved host name a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:23:43Z"
    - latency: 5.852452ms
      message: 'load-balancer-api-internal: tcp connection to a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:43Z"
    - latency: 6.327674ms
      message: 'load-balancer-api-internal: resolved host name a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:22:43Z"
    - latency: 4.42956ms
      message: 'load-balancer-api-internal: tcp connection to a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:21:43Z"
    - latency: 6.009353ms
      message: 'load-balancer-api-internal: resolved host name a19331c61c9b84c368c53f3eaa42d06d-fe1500935794c83d.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:21:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:49:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-249-to-network-check-target-ip-10-0-134-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-249.ec2.internal
      uid: e39f722b-a106-45ee-97e1-4a407053010d
    resourceVersion: "54753"
    uid: ab5ecb43-1863-45fb-99f5-a4e79e7e3444
  spec:
    sourcePod: network-check-source-869dcfcdcd-d9ldz
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:56:43Z"
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 845.292µs
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:43Z"
    - latency: 811.333µs
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:43Z"
    - latency: 773.832µs
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:43Z"
    - latency: 1.322068ms
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:21:43Z"
    - latency: 619.067µs
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:20:43Z"
    - latency: 798.113µs
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:19:43Z"
    - latency: 893.239µs
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:18:43Z"
    - latency: 959.829µs
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:43Z"
    - latency: 814.281µs
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:43Z"
    - latency: 1.182596ms
      message: 'network-check-target-ip-10-0-134-249: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:15:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:49:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-249-to-network-check-target-ip-10-0-137-236
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-249.ec2.internal
      uid: e39f722b-a106-45ee-97e1-4a407053010d
    resourceVersion: "54755"
    uid: fb50be16-d489-4f7f-b72f-b01ce4caacb0
  spec:
    sourcePod: network-check-source-869dcfcdcd-d9ldz
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:56:43Z"
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.043767ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:43Z"
    - latency: 1.677497ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:43Z"
    - latency: 1.960985ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:43Z"
    - latency: 2.023351ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:21:43Z"
    - latency: 2.098903ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:20:43Z"
    - latency: 2.137903ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:19:43Z"
    - latency: 1.634496ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:18:43Z"
    - latency: 1.993387ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:43Z"
    - latency: 1.952712ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:43Z"
    - latency: 2.1262ms
      message: 'network-check-target-ip-10-0-137-236: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:15:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:49:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-249-to-network-check-target-ip-10-0-139-1
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-249.ec2.internal
      uid: e39f722b-a106-45ee-97e1-4a407053010d
    resourceVersion: "54754"
    uid: 484e0d89-eff8-4a4e-926a-2f7ff74c330b
  spec:
    sourcePod: network-check-source-869dcfcdcd-d9ldz
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:56:43Z"
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.079777ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:43Z"
    - latency: 1.816629ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:43Z"
    - latency: 2.094075ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:43Z"
    - latency: 2.394825ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:21:43Z"
    - latency: 2.140803ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:20:43Z"
    - latency: 2.577025ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:19:43Z"
    - latency: 2.136507ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:18:43Z"
    - latency: 2.413446ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:17:43Z"
    - latency: 2.032812ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:16:43Z"
    - latency: 2.118943ms
      message: 'network-check-target-ip-10-0-139-1: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:15:43Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-09T18:49:42Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-249-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-249.ec2.internal
      uid: e39f722b-a106-45ee-97e1-4a407053010d
    resourceVersion: "55734"
    uid: 98dc5eb2-a54c-43df-9240-4dd92a24d8f7
  spec:
    sourcePod: network-check-source-869dcfcdcd-d9ldz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-09T18:55:43Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 826.233µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:25:43Z"
    - latency: 1.953055ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:25:43Z"
    - latency: 980.928µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:24:43Z"
    - latency: 1.609308ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:24:43Z"
    - latency: 830.889µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:23:43Z"
    - latency: 1.797817ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:23:43Z"
    - latency: 1.469583ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:22:43Z"
    - latency: 1.639263ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:22:43Z"
    - latency: 1.092823ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-09T19:21:43Z"
    - latency: 1.579413ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-09T19:21:43Z"
kind: List
metadata:
  resourceVersion: ""