apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T02:20:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-118-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-118.ec2.internal
      uid: 511a0d46-adc9-42fd-a665-c7fba8b0908f
    resourceVersion: "66613"
    uid: 43cf7515-8058-4c1d-aa13-4541c3d24694
  spec:
    sourcePod: network-check-source-6f8b768455-8cp89
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T02:27:53Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.142728ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:55:53Z"
    - latency: 1.065685ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:54:53Z"
    - latency: 1.532844ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:53:53Z"
    - latency: 1.248772ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:52:53Z"
    - latency: 1.093973ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:51:53Z"
    - latency: 1.101945ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:50:53Z"
    - latency: 1.10978ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:49:53Z"
    - latency: 1.303921ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:48:53Z"
    - latency: 1.186272ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:47:53Z"
    - latency: 1.122809ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:46:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T02:20:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-118-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-118.ec2.internal
      uid: 511a0d46-adc9-42fd-a665-c7fba8b0908f
    resourceVersion: "67245"
    uid: 62824ec4-fed8-4f4a-89fc-6a7188c9ba96
  spec:
    sourcePod: network-check-source-6f8b768455-8cp89
    targetEndpoint: a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T02:26:53Z"
      message: 'load-balancer-api-external: tcp connection to a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.15542ms
      message: 'load-balancer-api-external: tcp connection to a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:56:53Z"
    - latency: 8.588525ms
      message: 'load-balancer-api-external: resolved host name a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:56:53Z"
    - latency: 4.19555ms
      message: 'load-balancer-api-external: tcp connection to a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:55:53Z"
    - latency: 8.833688ms
      message: 'load-balancer-api-external: resolved host name a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:55:53Z"
    - latency: 4.704409ms
      message: 'load-balancer-api-external: tcp connection to a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:54:53Z"
    - latency: 7.236002ms
      message: 'load-balancer-api-external: resolved host name a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:54:53Z"
    - latency: 4.54683ms
      message: 'load-balancer-api-external: tcp connection to a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:53:53Z"
    - latency: 8.617284ms
      message: 'load-balancer-api-external: resolved host name a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:53:53Z"
    - latency: 5.302646ms
      message: 'load-balancer-api-external: tcp connection to a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:52:53Z"
    - latency: 8.209333ms
      message: 'load-balancer-api-external: resolved host name a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:52:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T02:20:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-118-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-118.ec2.internal
      uid: 511a0d46-adc9-42fd-a665-c7fba8b0908f
    resourceVersion: "67246"
    uid: 8cdcf07a-3e99-4285-a1a7-e79362eb3374
  spec:
    sourcePod: network-check-source-6f8b768455-8cp89
    targetEndpoint: a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T02:26:53Z"
      message: 'load-balancer-api-internal: tcp connection to a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.651249ms
      message: 'load-balancer-api-internal: tcp connection to a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:56:53Z"
    - latency: 8.539953ms
      message: 'load-balancer-api-internal: resolved host name a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:56:53Z"
    - latency: 4.814315ms
      message: 'load-balancer-api-internal: tcp connection to a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:55:53Z"
    - latency: 8.992106ms
      message: 'load-balancer-api-internal: resolved host name a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:55:53Z"
    - latency: 4.058991ms
      message: 'load-balancer-api-internal: tcp connection to a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:54:53Z"
    - latency: 7.175474ms
      message: 'load-balancer-api-internal: resolved host name a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:54:53Z"
    - latency: 4.899841ms
      message: 'load-balancer-api-internal: tcp connection to a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:53:53Z"
    - latency: 8.647941ms
      message: 'load-balancer-api-internal: resolved host name a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:53:53Z"
    - latency: 5.300604ms
      message: 'load-balancer-api-internal: tcp connection to a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:52:53Z"
    - latency: 8.18293ms
      message: 'load-balancer-api-internal: resolved host name a5a5bc31fa2d645b8b4d99986091c520-1a166a97d810ee87.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:52:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T02:20:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-118-to-network-check-target-ip-10-0-136-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-118.ec2.internal
      uid: 511a0d46-adc9-42fd-a665-c7fba8b0908f
    resourceVersion: "66610"
    uid: ec634733-bc07-4572-9ecb-549bca1a7e72
  spec:
    sourcePod: network-check-source-6f8b768455-8cp89
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T02:27:53Z"
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 898.047µs
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:55:53Z"
    - latency: 851.686µs
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:54:53Z"
    - latency: 1.651409ms
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:53:53Z"
    - latency: 1.332637ms
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:52:53Z"
    - latency: 892.586µs
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:51:53Z"
    - latency: 1.027697ms
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:50:53Z"
    - latency: 806.921µs
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:49:53Z"
    - latency: 904.336µs
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:48:53Z"
    - latency: 837.437µs
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:47:53Z"
    - latency: 1.727897ms
      message: 'network-check-target-ip-10-0-136-118: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:46:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T02:20:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-118-to-network-check-target-ip-10-0-139-191
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-118.ec2.internal
      uid: 511a0d46-adc9-42fd-a665-c7fba8b0908f
    resourceVersion: "66612"
    uid: 27855a69-500d-413e-b7e9-0727a4a5426b
  spec:
    sourcePod: network-check-source-6f8b768455-8cp89
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T02:27:53Z"
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.428062ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:55:53Z"
    - latency: 2.245253ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:54:53Z"
    - latency: 2.061257ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:53:53Z"
    - latency: 2.453504ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:52:53Z"
    - latency: 2.218167ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:51:53Z"
    - latency: 2.201348ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:50:53Z"
    - latency: 2.108853ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:49:53Z"
    - latency: 2.393671ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:48:53Z"
    - latency: 2.377345ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:47:53Z"
    - latency: 2.917274ms
      message: 'network-check-target-ip-10-0-139-191: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:46:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T02:20:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-118-to-network-check-target-ip-10-0-140-34
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-118.ec2.internal
      uid: 511a0d46-adc9-42fd-a665-c7fba8b0908f
    resourceVersion: "66611"
    uid: de6bfc22-db7c-4007-95bb-12c72de1fb3b
  spec:
    sourcePod: network-check-source-6f8b768455-8cp89
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T02:27:53Z"
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.970391ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:55:53Z"
    - latency: 1.944119ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:54:53Z"
    - latency: 2.042576ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:53:53Z"
    - latency: 1.928033ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:52:53Z"
    - latency: 2.213442ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:51:53Z"
    - latency: 2.054062ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:50:53Z"
    - latency: 1.997068ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:49:53Z"
    - latency: 2.374736ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:48:53Z"
    - latency: 2.499741ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:47:53Z"
    - latency: 3.075022ms
      message: 'network-check-target-ip-10-0-140-34: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:46:53Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-16T02:20:52Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-118-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-118.ec2.internal
      uid: 511a0d46-adc9-42fd-a665-c7fba8b0908f
    resourceVersion: "67244"
    uid: 3874ea25-83e1-4ef5-ac20-a7c3f24a1d6d
  spec:
    sourcePod: network-check-source-6f8b768455-8cp89
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-16T02:26:53Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.03169ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:56:53Z"
    - latency: 1.644219ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:56:53Z"
    - latency: 1.04699ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:55:53Z"
    - latency: 1.756488ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:55:53Z"
    - latency: 907.237µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:54:53Z"
    - latency: 1.611055ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:54:53Z"
    - latency: 795.346µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:53:53Z"
    - latency: 1.810466ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:53:53Z"
    - latency: 913.267µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-16T02:52:53Z"
    - latency: 1.801913ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-16T02:52:53Z"
kind: List
metadata:
  resourceVersion: ""