apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:22:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-53-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-53.ec2.internal
      uid: 63590df8-0006-4bb6-893d-074a9c60740f
    resourceVersion: "68237"
    uid: e6e1f8b3-bcf0-420a-b883-b9518a47807d
  spec:
    sourcePod: network-check-source-6f8b768455-kz6hm
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:29:23Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.100825ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:57:23Z"
    - latency: 1.108626ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:56:23Z"
    - latency: 770.409µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:55:23Z"
    - latency: 932.39µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:54:23Z"
    - latency: 886.528µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:53:23Z"
    - latency: 1.071996ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:52:23Z"
    - latency: 1.307614ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:51:23Z"
    - latency: 1.665961ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:50:23Z"
    - latency: 1.008442ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:49:23Z"
    - latency: 894.408µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:48:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:22:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-53-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-53.ec2.internal
      uid: 63590df8-0006-4bb6-893d-074a9c60740f
    resourceVersion: "69164"
    uid: e6d0d4af-08b4-4a17-b047-b6f27a53a924
  spec:
    sourcePod: network-check-source-6f8b768455-kz6hm
    targetEndpoint: a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:28:23Z"
      message: 'load-balancer-api-external: tcp connection to a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.202396ms
      message: 'load-balancer-api-external: tcp connection to a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:58:23Z"
    - latency: 9.479614ms
      message: 'load-balancer-api-external: resolved host name a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:58:23Z"
    - latency: 5.207993ms
      message: 'load-balancer-api-external: tcp connection to a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:57:23Z"
    - latency: 7.862012ms
      message: 'load-balancer-api-external: resolved host name a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:57:23Z"
    - latency: 4.031086ms
      message: 'load-balancer-api-external: tcp connection to a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:56:23Z"
    - latency: 6.645456ms
      message: 'load-balancer-api-external: resolved host name a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:56:23Z"
    - latency: 3.981842ms
      message: 'load-balancer-api-external: tcp connection to a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:55:23Z"
    - latency: 7.241582ms
      message: 'load-balancer-api-external: resolved host name a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:55:23Z"
    - latency: 4.966488ms
      message: 'load-balancer-api-external: tcp connection to a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:54:23Z"
    - latency: 6.123273ms
      message: 'load-balancer-api-external: resolved host name a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:54:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:22:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-53-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-53.ec2.internal
      uid: 63590df8-0006-4bb6-893d-074a9c60740f
    resourceVersion: "69165"
    uid: 24cee9ac-00d2-4627-8c2e-f8367abddbea
  spec:
    sourcePod: network-check-source-6f8b768455-kz6hm
    targetEndpoint: a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:28:23Z"
      message: 'load-balancer-api-internal: tcp connection to a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.149891ms
      message: 'load-balancer-api-internal: tcp connection to a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:58:23Z"
    - latency: 9.500905ms
      message: 'load-balancer-api-internal: resolved host name a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:58:23Z"
    - latency: 5.160848ms
      message: 'load-balancer-api-internal: tcp connection to a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:57:23Z"
    - latency: 7.898508ms
      message: 'load-balancer-api-internal: resolved host name a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:57:23Z"
    - latency: 4.023804ms
      message: 'load-balancer-api-internal: tcp connection to a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:56:23Z"
    - latency: 6.559356ms
      message: 'load-balancer-api-internal: resolved host name a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:56:23Z"
    - latency: 3.937204ms
      message: 'load-balancer-api-internal: tcp connection to a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:55:23Z"
    - latency: 7.178773ms
      message: 'load-balancer-api-internal: resolved host name a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:55:23Z"
    - latency: 4.948958ms
      message: 'load-balancer-api-internal: tcp connection to a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:54:23Z"
    - latency: 6.156513ms
      message: 'load-balancer-api-internal: resolved host name a5f73a95ab0404fa997ed8a9d488178f-28882c9994f0ebf9.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:54:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:22:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-53-to-network-check-target-ip-10-0-130-153
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-53.ec2.internal
      uid: 63590df8-0006-4bb6-893d-074a9c60740f
    resourceVersion: "68235"
    uid: 6957b48e-9bbc-424a-922b-4e47178c335b
  spec:
    sourcePod: network-check-source-6f8b768455-kz6hm
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:29:23Z"
      message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.66126ms
      message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:57:23Z"
    - latency: 2.11641ms
      message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:56:23Z"
    - latency: 1.914823ms
      message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:55:23Z"
    - latency: 2.231237ms
      message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:54:23Z"
    - latency: 2.092603ms
      message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:53:23Z"
    - latency: 2.370228ms
      message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:52:23Z"
    - latency: 2.338669ms
      message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:51:23Z"
    - latency: 2.068921ms
      message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:50:23Z"
    - latency: 2.621795ms
      message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:49:23Z"
    - latency: 1.983656ms
      message: 'network-check-target-ip-10-0-130-153: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:48:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:22:22Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-53-to-network-check-target-ip-10-0-137-141
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-53.ec2.internal
      uid: 63590df8-0006-4bb6-893d-074a9c60740f
    resourceVersion: "68236"
    uid: 05f859dc-097a-4a8c-8e68-37ca7ea068f8
  spec:
    sourcePod: network-check-source-6f8b768455-kz6hm
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:29:23Z"
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.627649ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:57:23Z"
    - latency: 2.787088ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:56:23Z"
    - latency: 2.339472ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:55:23Z"
    - latency: 2.323381ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:54:23Z"
    - latency: 2.341347ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:53:23Z"
    - latency: 2.370892ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:52:23Z"
    - latency: 1.981729ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:51:23Z"
    - latency: 2.704389ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:50:23Z"
    - latency: 2.658307ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:49:23Z"
    - latency: 2.787058ms
      message: 'network-check-target-ip-10-0-137-141: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:48:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:22:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-53-to-network-check-target-ip-10-0-139-53
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-53.ec2.internal
      uid: 63590df8-0006-4bb6-893d-074a9c60740f
    resourceVersion: "68234"
    uid: 5b804da9-cd1f-4307-9ced-96332e6ab42c
  spec:
    sourcePod: network-check-source-6f8b768455-kz6hm
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:29:23Z"
      message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 933.48µs
      message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:57:23Z"
    - latency: 1.394307ms
      message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:56:23Z"
    - latency: 1.252257ms
      message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:55:23Z"
    - latency: 956.206µs
      message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:54:23Z"
    - latency: 879.975µs
      message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:53:23Z"
    - latency: 1.040528ms
      message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:52:23Z"
    - latency: 984.674µs
      message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:51:23Z"
    - latency: 870.175µs
      message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:50:23Z"
    - latency: 1.446166ms
      message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:49:23Z"
    - latency: 965.336µs
      message: 'network-check-target-ip-10-0-139-53: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:48:23Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T03:22:21Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-53-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-53.ec2.internal
      uid: 63590df8-0006-4bb6-893d-074a9c60740f
    resourceVersion: "69163"
    uid: 98aa6c93-ca5a-497e-92d0-d93a7272ebe7
  spec:
    sourcePod: network-check-source-6f8b768455-kz6hm
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T03:28:23Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 966.536µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:58:23Z"
    - latency: 1.752035ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:58:23Z"
    - latency: 1.00649ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:57:23Z"
    - latency: 1.761316ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:57:23Z"
    - latency: 806.553µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:56:23Z"
    - latency: 2.008157ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:56:23Z"
    - latency: 1.530278ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:55:23Z"
    - latency: 1.808049ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:55:23Z"
    - latency: 865.018µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T03:54:23Z"
    - latency: 1.755328ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T03:54:23Z"
kind: List
metadata:
  resourceVersion: ""