apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:33:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-23-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-23.ec2.internal
      uid: 4032568d-10c6-4075-8401-7e2898ebf992
    resourceVersion: "55174"
    uid: d5158c67-b49b-4a86-8522-c37bfe9393c8
  spec:
    sourcePod: network-check-source-685456655f-qxfbv
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:40:58Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.003159ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:01:58Z"
    - latency: 1.065454ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:00:58Z"
    - latency: 1.379369ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:59:58Z"
    - latency: 1.426661ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:58:58Z"
    - latency: 1.295375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:57:58Z"
    - latency: 1.062305ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:56:58Z"
    - latency: 1.2858ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:55:58Z"
    - latency: 1.927919ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:54:58Z"
    - latency: 1.355153ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:53:58Z"
    - latency: 1.354255ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:52:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:33:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-23-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-23.ec2.internal
      uid: 4032568d-10c6-4075-8401-7e2898ebf992
    resourceVersion: "56781"
    uid: 70599f4a-a002-494f-8040-b02961fa2898
  spec:
    sourcePod: network-check-source-685456655f-qxfbv
    targetEndpoint: a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:39:58Z"
      message: 'load-balancer-api-external: tcp connection to a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.486685ms
      message: 'load-balancer-api-external: tcp connection to a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:03:58Z"
    - latency: 6.802272ms
      message: 'load-balancer-api-external: resolved host name a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:03:58Z"
    - latency: 4.367848ms
      message: 'load-balancer-api-external: tcp connection to a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:02:58Z"
    - latency: 6.74774ms
      message: 'load-balancer-api-external: resolved host name a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:02:58Z"
    - latency: 4.438575ms
      message: 'load-balancer-api-external: tcp connection to a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:01:58Z"
    - latency: 6.957315ms
      message: 'load-balancer-api-external: resolved host name a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:01:58Z"
    - latency: 4.170559ms
      message: 'load-balancer-api-external: tcp connection to a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:00:58Z"
    - latency: 6.527601ms
      message: 'load-balancer-api-external: resolved host name a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:00:58Z"
    - latency: 4.974366ms
      message: 'load-balancer-api-external: tcp connection to a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:59:58Z"
    - latency: 7.033043ms
      message: 'load-balancer-api-external: resolved host name a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T13:59:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:33:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-23-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-23.ec2.internal
      uid: 4032568d-10c6-4075-8401-7e2898ebf992
    resourceVersion: "56782"
    uid: d409ef1b-c682-4125-9fdc-2f9ed722cee2
  spec:
    sourcePod: network-check-source-685456655f-qxfbv
    targetEndpoint: a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:39:58Z"
      message: 'load-balancer-api-internal: tcp connection to a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.621087ms
      message: 'load-balancer-api-internal: tcp connection to a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:03:58Z"
    - latency: 6.749187ms
      message: 'load-balancer-api-internal: resolved host name a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:03:58Z"
    - latency: 4.422343ms
      message: 'load-balancer-api-internal: tcp connection to a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:02:58Z"
    - latency: 6.678682ms
      message: 'load-balancer-api-internal: resolved host name a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:02:58Z"
    - latency: 4.409524ms
      message: 'load-balancer-api-internal: tcp connection to a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:01:58Z"
    - latency: 6.908607ms
      message: 'load-balancer-api-internal: resolved host name a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:01:58Z"
    - latency: 4.181695ms
      message: 'load-balancer-api-internal: tcp connection to a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:00:58Z"
    - latency: 6.488861ms
      message: 'load-balancer-api-internal: resolved host name a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:00:58Z"
    - latency: 5.091975ms
      message: 'load-balancer-api-internal: tcp connection to a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:59:58Z"
    - latency: 7.011016ms
      message: 'load-balancer-api-internal: resolved host name a209ae3db84694a939a388515332a9c8-138fd676da6bc2a5.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T13:59:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:33:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-23-to-network-check-target-ip-10-0-129-230
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-23.ec2.internal
      uid: 4032568d-10c6-4075-8401-7e2898ebf992
    resourceVersion: "55172"
    uid: 03dd6621-5f68-417d-b74a-5bc7a6942be7
  spec:
    sourcePod: network-check-source-685456655f-qxfbv
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:40:58Z"
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.370344ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:01:58Z"
    - latency: 2.380666ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:00:58Z"
    - latency: 2.311676ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:59:58Z"
    - latency: 2.15405ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:58:58Z"
    - latency: 2.423486ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:57:58Z"
    - latency: 2.279471ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:56:58Z"
    - latency: 2.332449ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:55:58Z"
    - latency: 2.05624ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:54:58Z"
    - latency: 2.297995ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:53:58Z"
    - latency: 2.406933ms
      message: 'network-check-target-ip-10-0-129-230: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:52:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:33:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-23-to-network-check-target-ip-10-0-130-208
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-23.ec2.internal
      uid: 4032568d-10c6-4075-8401-7e2898ebf992
    resourceVersion: "55173"
    uid: 8fcf6fac-6936-480f-89e3-6e269806b598
  spec:
    sourcePod: network-check-source-685456655f-qxfbv
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:40:58Z"
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.345371ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:01:58Z"
    - latency: 2.396052ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:00:58Z"
    - latency: 2.283618ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:59:58Z"
    - latency: 2.298195ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:58:58Z"
    - latency: 2.217042ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:57:58Z"
    - latency: 1.978017ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:56:58Z"
    - latency: 2.023301ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:55:58Z"
    - latency: 1.85786ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:54:58Z"
    - latency: 2.190895ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:53:58Z"
    - latency: 2.073413ms
      message: 'network-check-target-ip-10-0-130-208: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:52:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:33:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-23-to-network-check-target-ip-10-0-140-23
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-23.ec2.internal
      uid: 4032568d-10c6-4075-8401-7e2898ebf992
    resourceVersion: "55171"
    uid: f9b073e5-61ec-43f5-8956-b79d7c4abf62
  spec:
    sourcePod: network-check-source-685456655f-qxfbv
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:40:58Z"
      message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.03487ms
      message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:01:58Z"
    - latency: 1.68729ms
      message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:00:58Z"
    - latency: 1.075586ms
      message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:59:58Z"
    - latency: 1.179624ms
      message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:58:58Z"
    - latency: 1.611455ms
      message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:57:58Z"
    - latency: 841.626µs
      message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:56:58Z"
    - latency: 823.019µs
      message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:55:58Z"
    - latency: 933.095µs
      message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:54:58Z"
    - latency: 1.270037ms
      message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:53:58Z"
    - latency: 1.176353ms
      message: 'network-check-target-ip-10-0-140-23: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:52:58Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-08T13:33:57Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-140-23-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-140-23.ec2.internal
      uid: 4032568d-10c6-4075-8401-7e2898ebf992
    resourceVersion: "56780"
    uid: 705f305d-a98f-4cef-89d7-6cb74553d344
  spec:
    sourcePod: network-check-source-685456655f-qxfbv
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-08T13:39:58Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.121153ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:03:58Z"
    - latency: 1.704648ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:03:58Z"
    - latency: 1.156316ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:02:58Z"
    - latency: 1.866966ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:02:58Z"
    - latency: 1.320069ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:01:58Z"
    - latency: 1.999416ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:01:58Z"
    - latency: 1.289545ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T14:00:58Z"
    - latency: 1.962855ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T14:00:58Z"
    - latency: 1.312171ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-08T13:59:58Z"
    - latency: 1.695963ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-08T13:59:58Z"
kind: List
metadata:
  resourceVersion: ""