apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T12:20:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-145-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-145.ec2.internal
      uid: c0ab48ca-f3c5-4c04-8d4e-43e72a40e97e
    resourceVersion: "53776"
    uid: d9f094d7-8fbf-4396-9b7b-c619180a442e
  spec:
    sourcePod: network-check-source-685456655f-j2qn7
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T12:27:57Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.128471ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:48:57Z"
    - latency: 1.429384ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:47:57Z"
    - latency: 866.651µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:46:57Z"
    - latency: 1.068136ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:45:57Z"
    - latency: 986.448µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:44:57Z"
    - latency: 1.472923ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:43:57Z"
    - latency: 790.463µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:42:57Z"
    - latency: 1.25311ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:41:57Z"
    - latency: 1.48558ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:40:57Z"
    - latency: 952.177µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:39:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T12:20:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-145-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-145.ec2.internal
      uid: c0ab48ca-f3c5-4c04-8d4e-43e72a40e97e
    resourceVersion: "55323"
    uid: e1884fad-c0b8-42a0-91a6-4822dd0dcdca
  spec:
    sourcePod: network-check-source-685456655f-j2qn7
    targetEndpoint: a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T12:26:57Z"
      message: 'load-balancer-api-external: tcp connection to a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.299717ms
      message: 'load-balancer-api-external: tcp connection to a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:50:57Z"
    - latency: 7.198784ms
      message: 'load-balancer-api-external: resolved host name a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:50:57Z"
    - latency: 4.339936ms
      message: 'load-balancer-api-external: tcp connection to a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:49:57Z"
    - latency: 8.186272ms
      message: 'load-balancer-api-external: resolved host name a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:49:57Z"
    - latency: 5.006729ms
      message: 'load-balancer-api-external: tcp connection to a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:48:57Z"
    - latency: 7.08382ms
      message: 'load-balancer-api-external: resolved host name a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:48:57Z"
    - latency: 4.087814ms
      message: 'load-balancer-api-external: tcp connection to a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:47:57Z"
    - latency: 6.981286ms
      message: 'load-balancer-api-external: resolved host name a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:47:57Z"
    - latency: 6.148163ms
      message: 'load-balancer-api-external: tcp connection to a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:46:57Z"
    - latency: 7.027848ms
      message: 'load-balancer-api-external: resolved host name a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:46:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T12:20:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-145-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-145.ec2.internal
      uid: c0ab48ca-f3c5-4c04-8d4e-43e72a40e97e
    resourceVersion: "55324"
    uid: dc630b98-a74e-456f-8944-7bf280e76ca3
  spec:
    sourcePod: network-check-source-685456655f-j2qn7
    targetEndpoint: a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T12:26:57Z"
      message: 'load-balancer-api-internal: tcp connection to a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.288036ms
      message: 'load-balancer-api-internal: tcp connection to a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:50:57Z"
    - latency: 7.272203ms
      message: 'load-balancer-api-internal: resolved host name a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:50:57Z"
    - latency: 4.307234ms
      message: 'load-balancer-api-internal: tcp connection to a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:49:57Z"
    - latency: 8.15754ms
      message: 'load-balancer-api-internal: resolved host name a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:49:57Z"
    - latency: 5.0207ms
      message: 'load-balancer-api-internal: tcp connection to a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:48:57Z"
    - latency: 7.150417ms
      message: 'load-balancer-api-internal: resolved host name a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:48:57Z"
    - latency: 4.166403ms
      message: 'load-balancer-api-internal: tcp connection to a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:47:57Z"
    - latency: 6.934628ms
      message: 'load-balancer-api-internal: resolved host name a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:47:57Z"
    - latency: 6.153301ms
      message: 'load-balancer-api-internal: tcp connection to a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:46:57Z"
    - latency: 7.104215ms
      message: 'load-balancer-api-internal: resolved host name a01e5a04a857a4e5f9f32c22dafab9d3-ada1b694c0aa7dcc.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:46:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T12:20:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-145-to-network-check-target-ip-10-0-130-145
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-145.ec2.internal
      uid: c0ab48ca-f3c5-4c04-8d4e-43e72a40e97e
    resourceVersion: "53773"
    uid: 163f6781-0ef1-429d-b051-7c0b87d45019
  spec:
    sourcePod: network-check-source-685456655f-j2qn7
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T12:27:57Z"
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 974.779µs
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:48:57Z"
    - latency: 1.084301ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:47:57Z"
    - latency: 1.149203ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:46:57Z"
    - latency: 1.117983ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:45:57Z"
    - latency: 959.446µs
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:44:57Z"
    - latency: 1.701255ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:43:57Z"
    - latency: 1.108092ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:42:57Z"
    - latency: 1.469833ms
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:41:57Z"
    - latency: 925.373µs
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:40:57Z"
    - latency: 824.196µs
      message: 'network-check-target-ip-10-0-130-145: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:39:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T12:20:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-145-to-network-check-target-ip-10-0-132-159
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-145.ec2.internal
      uid: c0ab48ca-f3c5-4c04-8d4e-43e72a40e97e
    resourceVersion: "53774"
    uid: 49c73c18-14eb-454a-81c3-da26e4ab703b
  spec:
    sourcePod: network-check-source-685456655f-j2qn7
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T12:27:57Z"
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.776883ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:48:57Z"
    - latency: 1.827349ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:47:57Z"
    - latency: 2.223929ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:46:57Z"
    - latency: 2.718293ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:45:57Z"
    - latency: 2.248116ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:44:57Z"
    - latency: 1.999237ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:43:57Z"
    - latency: 1.750972ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:42:57Z"
    - latency: 2.017416ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:41:57Z"
    - latency: 1.710798ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:40:57Z"
    - latency: 2.183986ms
      message: 'network-check-target-ip-10-0-132-159: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:39:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T12:20:56Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-145-to-network-check-target-ip-10-0-134-80
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-145.ec2.internal
      uid: c0ab48ca-f3c5-4c04-8d4e-43e72a40e97e
    resourceVersion: "53775"
    uid: 64864845-2a3f-4600-ad80-7721441be351
  spec:
    sourcePod: network-check-source-685456655f-j2qn7
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T12:27:57Z"
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.938053ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:48:57Z"
    - latency: 1.994435ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:47:57Z"
    - latency: 2.068602ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:46:57Z"
    - latency: 2.64173ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:45:57Z"
    - latency: 2.352246ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:44:57Z"
    - latency: 1.981876ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:43:57Z"
    - latency: 1.933638ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:42:57Z"
    - latency: 2.120225ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:41:57Z"
    - latency: 2.070592ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:40:57Z"
    - latency: 2.177454ms
      message: 'network-check-target-ip-10-0-134-80: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:39:57Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-06T12:20:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-130-145-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-130-145.ec2.internal
      uid: c0ab48ca-f3c5-4c04-8d4e-43e72a40e97e
    resourceVersion: "55322"
    uid: 97b388e5-2dca-4f99-afd7-a49bee24a8b7
  spec:
    sourcePod: network-check-source-685456655f-j2qn7
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-06T12:26:57Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 955.52µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:50:57Z"
    - latency: 1.724983ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:50:57Z"
    - latency: 1.07242ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:49:57Z"
    - latency: 1.737649ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:49:57Z"
    - latency: 878.006µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:48:57Z"
    - latency: 1.923334ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:48:57Z"
    - latency: 787.644µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:47:57Z"
    - latency: 2.189122ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:47:57Z"
    - latency: 1.092186ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-06T12:46:57Z"
    - latency: 1.725095ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-06T12:46:57Z"
kind: List
metadata:
  resourceVersion: ""