apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:17:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-94-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-94.ec2.internal
      uid: 79422f05-e627-452f-9d0a-0b85cdd61d67
    resourceVersion: "149641"
    uid: c6070451-503e-413d-b8a6-8c76a3fc4814
  spec:
    sourcePod: network-check-source-6f78d59f99-9xtxc
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:24:29Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.009736ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:20:29Z"
    - latency: 1.555187ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:19:29Z"
    - latency: 1.018684ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:18:29Z"
    - latency: 1.636328ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:17:29Z"
    - latency: 908.665µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:16:29Z"
    - latency: 1.182687ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:15:29Z"
    - latency: 1.398649ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:14:29Z"
    - latency: 828.955µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:13:29Z"
    - latency: 1.185303ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:12:29Z"
    - latency: 1.334016ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:11:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:17:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-94-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-94.ec2.internal
      uid: 79422f05-e627-452f-9d0a-0b85cdd61d67
    resourceVersion: "147287"
    uid: b563e505-aef5-4ae5-b43b-11da5335968e
  spec:
    sourcePod: network-check-source-6f78d59f99-9xtxc
    targetEndpoint: a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:23:29Z"
      message: 'load-balancer-api-external: tcp connection to a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 13.715307ms
      message: 'load-balancer-api-external: tcp connection to a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:17:29Z"
    - latency: 7.160184ms
      message: 'load-balancer-api-external: resolved host name a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:17:29Z"
    - latency: 16.936324ms
      message: 'load-balancer-api-external: tcp connection to a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:16:29Z"
    - latency: 7.826964ms
      message: 'load-balancer-api-external: resolved host name a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:16:29Z"
    - latency: 16.978295ms
      message: 'load-balancer-api-external: tcp connection to a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:15:29Z"
    - latency: 6.836607ms
      message: 'load-balancer-api-external: resolved host name a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:15:29Z"
    - latency: 18.007007ms
      message: 'load-balancer-api-external: tcp connection to a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:14:29Z"
    - latency: 7.641354ms
      message: 'load-balancer-api-external: resolved host name a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:14:29Z"
    - latency: 16.403494ms
      message: 'load-balancer-api-external: tcp connection to a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:13:29Z"
    - latency: 8.290998ms
      message: 'load-balancer-api-external: resolved host name a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:13:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:17:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-94-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-94.ec2.internal
      uid: 79422f05-e627-452f-9d0a-0b85cdd61d67
    resourceVersion: "147288"
    uid: 8df9d993-bcec-4a93-8a56-608a7b7d316e
  spec:
    sourcePod: network-check-source-6f78d59f99-9xtxc
    targetEndpoint: a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:23:29Z"
      message: 'load-balancer-api-internal: tcp connection to a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 15.243158ms
      message: 'load-balancer-api-internal: tcp connection to a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:17:29Z"
    - latency: 7.063557ms
      message: 'load-balancer-api-internal: resolved host name a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:17:29Z"
    - latency: 16.385988ms
      message: 'load-balancer-api-internal: tcp connection to a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:16:29Z"
    - latency: 7.671421ms
      message: 'load-balancer-api-internal: resolved host name a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:16:29Z"
    - latency: 17.03303ms
      message: 'load-balancer-api-internal: tcp connection to a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:15:29Z"
    - latency: 6.741137ms
      message: 'load-balancer-api-internal: resolved host name a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:15:29Z"
    - latency: 16.181787ms
      message: 'load-balancer-api-internal: tcp connection to a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:14:29Z"
    - latency: 7.578142ms
      message: 'load-balancer-api-internal: resolved host name a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:14:29Z"
    - latency: 14.813164ms
      message: 'load-balancer-api-internal: tcp connection to a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:13:29Z"
    - latency: 8.220922ms
      message: 'load-balancer-api-internal: resolved host name a5b593b5fe01a4b459dee98cc65e601a-e829f27606018762.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:13:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:17:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-94-to-network-check-target-ip-10-0-133-251
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-94.ec2.internal
      uid: 79422f05-e627-452f-9d0a-0b85cdd61d67
    resourceVersion: "149639"
    uid: f765a1c5-2942-44aa-8df7-a6291bb099d6
  spec:
    sourcePod: network-check-source-6f78d59f99-9xtxc
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:24:29Z"
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.898974ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:20:29Z"
    - latency: 2.294089ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:19:29Z"
    - latency: 2.53865ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:18:29Z"
    - latency: 2.185063ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:17:29Z"
    - latency: 3.479261ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:16:29Z"
    - latency: 2.214392ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:15:29Z"
    - latency: 2.242273ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:14:29Z"
    - latency: 1.81644ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:13:29Z"
    - latency: 2.11652ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:12:29Z"
    - latency: 2.656132ms
      message: 'network-check-target-ip-10-0-133-251: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:11:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:17:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-94-to-network-check-target-ip-10-0-134-94
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-94.ec2.internal
      uid: 79422f05-e627-452f-9d0a-0b85cdd61d67
    resourceVersion: "149638"
    uid: 160114f2-a59a-4833-b97f-4d6a0641c64a
  spec:
    sourcePod: network-check-source-6f78d59f99-9xtxc
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:24:29Z"
      message: 'network-check-target-ip-10-0-134-94: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.565129ms
      message: 'network-check-target-ip-10-0-134-94: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:20:29Z"
    - latency: 815.742µs
      message: 'network-check-target-ip-10-0-134-94: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:19:29Z"
    - latency: 762.688µs
      message: 'network-check-target-ip-10-0-134-94: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:18:29Z"
    - latency: 759.794µs
      message: 'network-check-target-ip-10-0-134-94: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:17:29Z"
    - latency: 1.040951ms
      message: 'network-check-target-ip-10-0-134-94: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:16:29Z"
    - latency: 876.551µs
      message: 'network-check-target-ip-10-0-134-94: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:15:29Z"
    - latency: 793.8µs
      message: 'network-check-target-ip-10-0-134-94: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:14:29Z"
    - latency: 779.754µs
      message: 'network-check-target-ip-10-0-134-94: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:13:29Z"
    - latency: 914.44µs
      message: 'network-check-target-ip-10-0-134-94: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:12:29Z"
    - latency: 975.362µs
      message: 'network-check-target-ip-10-0-134-94: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:11:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:17:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-94-to-network-check-target-ip-10-0-139-29
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-94.ec2.internal
      uid: 79422f05-e627-452f-9d0a-0b85cdd61d67
    resourceVersion: "149640"
    uid: 82057cd0-0e52-40ac-9828-012377850184
  spec:
    sourcePod: network-check-source-6f78d59f99-9xtxc
    targetEndpoint: 10.133.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:24:29Z"
      message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.76622ms
      message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:20:29Z"
    - latency: 2.299591ms
      message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:19:29Z"
    - latency: 2.074735ms
      message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:18:29Z"
    - latency: 2.491161ms
      message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:17:29Z"
    - latency: 2.545409ms
      message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:16:29Z"
    - latency: 2.420353ms
      message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:15:29Z"
    - latency: 2.540671ms
      message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:14:29Z"
    - latency: 3.004602ms
      message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:13:29Z"
    - latency: 2.005475ms
      message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:12:29Z"
    - latency: 2.704398ms
      message: 'network-check-target-ip-10-0-139-29: tcp connection to 10.133.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:11:29Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-10-29T22:17:29Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-134-94-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-134-94.ec2.internal
      uid: 79422f05-e627-452f-9d0a-0b85cdd61d67
    resourceVersion: "147283"
    uid: f3b14e5f-1cfd-48dc-850a-9d9ba5104066
  spec:
    sourcePod: network-check-source-6f78d59f99-9xtxc
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-10-29T22:23:29Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 933.621µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:17:29Z"
    - latency: 2.308066ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:17:29Z"
    - latency: 1.051822ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:16:29Z"
    - latency: 1.866847ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:16:29Z"
    - latency: 1.319415ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:15:29Z"
    - latency: 1.816845ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:15:29Z"
    - latency: 965.329µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:14:29Z"
    - latency: 1.716553ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:14:29Z"
    - latency: 994.878µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-10-29T23:13:29Z"
    - latency: 2.69902ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-10-29T23:13:29Z"
kind: List
metadata:
  resourceVersion: ""