apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:28:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: 41824b35-70b0-4b60-aaa8-56d8ce8fe747
    resourceVersion: "40898"
    uid: d26c1018-e07a-42fe-80fa-227fe4ef59ec
  spec:
    sourcePod: network-check-source-7cbc45fddc-c5sfz
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:35:47Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.256385ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:17:47Z"
    - latency: 1.247283ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:16:47Z"
    - latency: 1.512068ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:15:47Z"
    - latency: 1.038419ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:14:47Z"
    - latency: 1.231243ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:13:47Z"
    - latency: 881.892µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:12:47Z"
    - latency: 1.253131ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:11:47Z"
    - latency: 1.236972ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:10:47Z"
    - latency: 887.497µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:09:47Z"
    - latency: 952.122µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:08:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:28:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: 41824b35-70b0-4b60-aaa8-56d8ce8fe747
    resourceVersion: "40354"
    uid: a03c3a52-9b8b-4b9e-adcb-e2e7c3bf7b0b
  spec:
    sourcePod: network-check-source-7cbc45fddc-c5sfz
    targetEndpoint: a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:34:47Z"
      message: 'load-balancer-api-external: tcp connection to a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.177666ms
      message: 'load-balancer-api-external: tcp connection to a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:16:47Z"
    - latency: 8.013179ms
      message: 'load-balancer-api-external: resolved host name a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:16:47Z"
    - latency: 4.84307ms
      message: 'load-balancer-api-external: tcp connection to a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:15:47Z"
    - latency: 8.899874ms
      message: 'load-balancer-api-external: resolved host name a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:15:47Z"
    - latency: 5.733312ms
      message: 'load-balancer-api-external: tcp connection to a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:14:47Z"
    - latency: 8.458943ms
      message: 'load-balancer-api-external: resolved host name a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:14:47Z"
    - latency: 5.087633ms
      message: 'load-balancer-api-external: tcp connection to a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:13:47Z"
    - latency: 8.989828ms
      message: 'load-balancer-api-external: resolved host name a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:13:47Z"
    - latency: 5.28858ms
      message: 'load-balancer-api-external: tcp connection to a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:12:47Z"
    - latency: 8.571724ms
      message: 'load-balancer-api-external: resolved host name a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:12:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:28:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: 41824b35-70b0-4b60-aaa8-56d8ce8fe747
    resourceVersion: "40353"
    uid: 7bb7c762-2b63-45b9-8728-35febaa88b7e
  spec:
    sourcePod: network-check-source-7cbc45fddc-c5sfz
    targetEndpoint: a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:34:47Z"
      message: 'load-balancer-api-internal: tcp connection to a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.148367ms
      message: 'load-balancer-api-internal: tcp connection to a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:16:47Z"
    - latency: 8.057687ms
      message: 'load-balancer-api-internal: resolved host name a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:16:47Z"
    - latency: 4.793318ms
      message: 'load-balancer-api-internal: tcp connection to a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:15:47Z"
    - latency: 8.876672ms
      message: 'load-balancer-api-internal: resolved host name a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:15:47Z"
    - latency: 5.757611ms
      message: 'load-balancer-api-internal: tcp connection to a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:14:47Z"
    - latency: 8.401102ms
      message: 'load-balancer-api-internal: resolved host name a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:14:47Z"
    - latency: 3.724532ms
      message: 'load-balancer-api-internal: tcp connection to a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:13:47Z"
    - latency: 8.926783ms
      message: 'load-balancer-api-internal: resolved host name a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:13:47Z"
    - latency: 5.357449ms
      message: 'load-balancer-api-internal: tcp connection to a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:12:47Z"
    - latency: 8.548616ms
      message: 'load-balancer-api-internal: resolved host name a5391e51d7e224ba891043367c3b34bf-660b2d6ada90a295.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:12:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:28:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-network-check-target-ip-10-0-136-228
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: 41824b35-70b0-4b60-aaa8-56d8ce8fe747
    resourceVersion: "40896"
    uid: 05d435de-487a-43b6-bbfa-25588c9b40ca
  spec:
    sourcePod: network-check-source-7cbc45fddc-c5sfz
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:35:47Z"
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.2201ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:17:47Z"
    - latency: 2.003449ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:16:47Z"
    - latency: 1.941645ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:15:47Z"
    - latency: 2.107723ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:14:47Z"
    - latency: 2.016923ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:13:47Z"
    - latency: 1.9575ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:12:47Z"
    - latency: 1.829657ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:11:47Z"
    - latency: 1.974862ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:10:47Z"
    - latency: 2.186468ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:09:47Z"
    - latency: 1.858632ms
      message: 'network-check-target-ip-10-0-136-228: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:08:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:28:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-network-check-target-ip-10-0-136-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: 41824b35-70b0-4b60-aaa8-56d8ce8fe747
    resourceVersion: "40895"
    uid: fc0bd085-ae01-4175-a2ec-b6968ec892d3
  spec:
    sourcePod: network-check-source-7cbc45fddc-c5sfz
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:35:47Z"
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.352961ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:17:47Z"
    - latency: 1.137123ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:16:47Z"
    - latency: 917.587µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:15:47Z"
    - latency: 1.154429ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:14:47Z"
    - latency: 1.024005ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:13:47Z"
    - latency: 1.116851ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:12:47Z"
    - latency: 1.050329ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:11:47Z"
    - latency: 1.078095ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:10:47Z"
    - latency: 820.962µs
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:09:47Z"
    - latency: 1.02487ms
      message: 'network-check-target-ip-10-0-136-99: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:08:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:28:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-network-check-target-ip-10-0-141-178
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: 41824b35-70b0-4b60-aaa8-56d8ce8fe747
    resourceVersion: "40897"
    uid: 966bd4c7-2f7c-4e00-a63f-2ecc3d45b38e
  spec:
    sourcePod: network-check-source-7cbc45fddc-c5sfz
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:35:47Z"
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.165837ms
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:17:47Z"
    - latency: 2.401748ms
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:16:47Z"
    - latency: 2.535775ms
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:15:47Z"
    - latency: 2.772483ms
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:14:47Z"
    - latency: 1.988089ms
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:13:47Z"
    - latency: 2.156896ms
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:12:47Z"
    - latency: 2.14499ms
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:11:47Z"
    - latency: 2.254571ms
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:10:47Z"
    - latency: 2.433882ms
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:09:47Z"
    - latency: 2.181652ms
      message: 'network-check-target-ip-10-0-141-178: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:08:47Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-19T08:28:46Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-99.ec2.internal
      uid: 41824b35-70b0-4b60-aaa8-56d8ce8fe747
    resourceVersion: "40352"
    uid: 7b375c9d-d6cc-4fb4-a27e-6b6b345a1f8f
  spec:
    sourcePod: network-check-source-7cbc45fddc-c5sfz
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-19T08:34:47Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.049597ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:16:47Z"
    - latency: 2.271063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:16:47Z"
    - latency: 901.579µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:15:47Z"
    - latency: 1.798079ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:15:47Z"
    - latency: 1.041236ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:14:47Z"
    - latency: 1.720139ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:14:47Z"
    - latency: 850.487µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:13:47Z"
    - latency: 2.382445ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:13:47Z"
    - latency: 1.080285ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-19T09:12:47Z"
    - latency: 1.878732ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-19T09:12:47Z"
kind: List
metadata:
  resourceVersion: ""