apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T17:30:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-21-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-21.ec2.internal
      uid: 4ba4cfbc-85e5-4c2a-9eee-b7ddf5ea658d
    resourceVersion: "32683"
    uid: 65783d59-15eb-48da-b207-b3493108a677
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cgrlr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T17:37:11Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 758.835µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:12:11Z"
    - latency: 1.538387ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:11:11Z"
    - latency: 1.361001ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:10:11Z"
    - latency: 918.986µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:09:11Z"
    - latency: 837.375µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:08:11Z"
    - latency: 845.763µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:07:11Z"
    - latency: 798.388µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:06:11Z"
    - latency: 794.185µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:05:11Z"
    - latency: 1.049047ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:04:11Z"
    - latency: 1.055897ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:03:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T17:30:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-21-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-21.ec2.internal
      uid: 4ba4cfbc-85e5-4c2a-9eee-b7ddf5ea658d
    resourceVersion: "32684"
    uid: ad45d351-85f8-49f9-aabe-e75175b5ecd6
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cgrlr
    targetEndpoint: a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T17:36:11Z"
      message: 'load-balancer-api-external: tcp connection to a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.740638ms
      message: 'load-balancer-api-external: tcp connection to a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:12:11Z"
    - latency: 8.731941ms
      message: 'load-balancer-api-external: resolved host name a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:12:11Z"
    - latency: 3.486891ms
      message: 'load-balancer-api-external: tcp connection to a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:11:11Z"
    - latency: 8.77089ms
      message: 'load-balancer-api-external: resolved host name a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:11:11Z"
    - latency: 7.005038ms
      message: 'load-balancer-api-external: tcp connection to a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:10:11Z"
    - latency: 8.374348ms
      message: 'load-balancer-api-external: resolved host name a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:10:11Z"
    - latency: 4.846008ms
      message: 'load-balancer-api-external: tcp connection to a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:09:11Z"
    - latency: 8.684425ms
      message: 'load-balancer-api-external: resolved host name a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:09:11Z"
    - latency: 5.382064ms
      message: 'load-balancer-api-external: tcp connection to a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:08:11Z"
    - latency: 8.768359ms
      message: 'load-balancer-api-external: resolved host name a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:08:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T17:30:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-21-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-21.ec2.internal
      uid: 4ba4cfbc-85e5-4c2a-9eee-b7ddf5ea658d
    resourceVersion: "32685"
    uid: 1ecd2ca6-d807-4093-8ceb-f7f3b2cfd2d9
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cgrlr
    targetEndpoint: a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T17:36:11Z"
      message: 'load-balancer-api-internal: tcp connection to a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.810157ms
      message: 'load-balancer-api-internal: tcp connection to a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:12:11Z"
    - latency: 8.66837ms
      message: 'load-balancer-api-internal: resolved host name a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:12:11Z"
    - latency: 4.37964ms
      message: 'load-balancer-api-internal: tcp connection to a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:11:11Z"
    - latency: 8.66642ms
      message: 'load-balancer-api-internal: resolved host name a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:11:11Z"
    - latency: 4.910904ms
      message: 'load-balancer-api-internal: tcp connection to a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:10:11Z"
    - latency: 8.323903ms
      message: 'load-balancer-api-internal: resolved host name a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:10:11Z"
    - latency: 5.020127ms
      message: 'load-balancer-api-internal: tcp connection to a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:09:11Z"
    - latency: 8.62847ms
      message: 'load-balancer-api-internal: resolved host name a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:09:11Z"
    - latency: 5.362075ms
      message: 'load-balancer-api-internal: tcp connection to a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:08:11Z"
    - latency: 8.685231ms
      message: 'load-balancer-api-internal: resolved host name a5f5f24e3e3734304bc0eecd774795ff-9ee6d29c28677ff5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:08:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T17:30:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-21-to-network-check-target-ip-10-0-132-249
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-21.ec2.internal
      uid: 4ba4cfbc-85e5-4c2a-9eee-b7ddf5ea658d
    resourceVersion: "32679"
    uid: bf634f16-ba29-4121-93eb-7309080e6520
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cgrlr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T17:37:11Z"
      message: 'network-check-target-ip-10-0-132-249: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.57903ms
      message: 'network-check-target-ip-10-0-132-249: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:12:11Z"
    - latency: 1.48783ms
      message: 'network-check-target-ip-10-0-132-249: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:11:11Z"
    - latency: 1.621797ms
      message: 'network-check-target-ip-10-0-132-249: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:10:11Z"
    - latency: 1.528512ms
      message: 'network-check-target-ip-10-0-132-249: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:09:11Z"
    - latency: 1.734179ms
      message: 'network-check-target-ip-10-0-132-249: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:08:11Z"
    - latency: 1.565843ms
      message: 'network-check-target-ip-10-0-132-249: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:07:11Z"
    - latency: 1.504699ms
      message: 'network-check-target-ip-10-0-132-249: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:06:11Z"
    - latency: 1.290235ms
      message: 'network-check-target-ip-10-0-132-249: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:05:11Z"
    - latency: 1.891918ms
      message: 'network-check-target-ip-10-0-132-249: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:04:11Z"
    - latency: 1.532516ms
      message: 'network-check-target-ip-10-0-132-249: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:03:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T17:30:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-21-to-network-check-target-ip-10-0-135-98
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-21.ec2.internal
      uid: 4ba4cfbc-85e5-4c2a-9eee-b7ddf5ea658d
    resourceVersion: "32680"
    uid: 17d1de7c-2e87-43e7-9340-e352836d2db8
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cgrlr
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T17:37:11Z"
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.752157ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:12:11Z"
    - latency: 1.753409ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:11:11Z"
    - latency: 1.776653ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:10:11Z"
    - latency: 1.830849ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:09:11Z"
    - latency: 1.93921ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:08:11Z"
    - latency: 1.893461ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:07:11Z"
    - latency: 1.777863ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:06:11Z"
    - latency: 1.818381ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:05:11Z"
    - latency: 1.995287ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:04:11Z"
    - latency: 1.763137ms
      message: 'network-check-target-ip-10-0-135-98: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:03:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T17:30:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-21-to-network-check-target-ip-10-0-136-21
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-21.ec2.internal
      uid: 4ba4cfbc-85e5-4c2a-9eee-b7ddf5ea658d
    resourceVersion: "32681"
    uid: 92c31e25-8d66-4717-a08d-29572165e3ca
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cgrlr
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T17:37:11Z"
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.245491ms
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:12:11Z"
    - latency: 868.837µs
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:11:11Z"
    - latency: 970.027µs
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:10:11Z"
    - latency: 1.363264ms
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:09:11Z"
    - latency: 869.092µs
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:08:11Z"
    - latency: 1.196377ms
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:07:11Z"
    - latency: 781.654µs
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:06:11Z"
    - latency: 732.49µs
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:05:11Z"
    - latency: 1.300769ms
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:04:11Z"
    - latency: 793.718µs
      message: 'network-check-target-ip-10-0-136-21: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:03:11Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-21T17:30:10Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-21-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-21.ec2.internal
      uid: 4ba4cfbc-85e5-4c2a-9eee-b7ddf5ea658d
    resourceVersion: "32682"
    uid: b0881faa-6da3-42fe-9d48-405d5e191038
  spec:
    sourcePod: network-check-source-7bc5b6bf85-cgrlr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-21T17:36:11Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.024143ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:12:11Z"
    - latency: 1.832618ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:12:11Z"
    - latency: 794.874µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:11:11Z"
    - latency: 1.978063ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:11:11Z"
    - latency: 952.421µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:10:11Z"
    - latency: 1.840409ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:10:11Z"
    - latency: 692.785µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:09:11Z"
    - latency: 1.922533ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:09:11Z"
    - latency: 763.143µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-21T18:08:11Z"
    - latency: 1.696284ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-21T18:08:11Z"
kind: List
metadata:
  resourceVersion: ""