apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T21:45:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-7-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-7.ec2.internal
      uid: cbba0146-7c1b-438e-8d4b-13874e334160
    resourceVersion: "67019"
    uid: 6aaf3c0c-72ec-462e-be1b-5f47372f4216
  spec:
    sourcePod: network-check-source-7cbc45fddc-9vpfj
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:52:36Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.173375ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:20:36Z"
    - latency: 988.82µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:19:36Z"
    - latency: 1.148909ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:18:36Z"
    - latency: 1.105539ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:17:36Z"
    - latency: 1.030324ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:16:36Z"
    - latency: 1.021154ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:15:36Z"
    - latency: 1.102976ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:14:36Z"
    - latency: 1.126678ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:13:36Z"
    - latency: 1.357994ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:12:36Z"
    - latency: 1.026508ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:11:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T21:45:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-7-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-7.ec2.internal
      uid: cbba0146-7c1b-438e-8d4b-13874e334160
    resourceVersion: "67473"
    uid: 4f5c440c-bb7d-4e6b-82b8-5db473138bf2
  spec:
    sourcePod: network-check-source-7cbc45fddc-9vpfj
    targetEndpoint: a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:51:36Z"
      message: 'load-balancer-api-external: tcp connection to a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.825816ms
      message: 'load-balancer-api-external: tcp connection to a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:21:36Z"
    - latency: 8.238217ms
      message: 'load-balancer-api-external: resolved host name a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:21:36Z"
    - latency: 5.373554ms
      message: 'load-balancer-api-external: tcp connection to a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:20:36Z"
    - latency: 9.621598ms
      message: 'load-balancer-api-external: resolved host name a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:20:36Z"
    - latency: 5.064053ms
      message: 'load-balancer-api-external: tcp connection to a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:19:36Z"
    - latency: 6.938479ms
      message: 'load-balancer-api-external: resolved host name a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:19:36Z"
    - latency: 4.839214ms
      message: 'load-balancer-api-external: tcp connection to a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:18:36Z"
    - latency: 6.90854ms
      message: 'load-balancer-api-external: resolved host name a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:18:36Z"
    - latency: 4.754871ms
      message: 'load-balancer-api-external: tcp connection to a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:17:36Z"
    - latency: 7.996916ms
      message: 'load-balancer-api-external: resolved host name a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:17:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T21:45:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-7-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-7.ec2.internal
      uid: cbba0146-7c1b-438e-8d4b-13874e334160
    resourceVersion: "67474"
    uid: b7816be7-9114-4850-b55d-fe24bb1c13d2
  spec:
    sourcePod: network-check-source-7cbc45fddc-9vpfj
    targetEndpoint: a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:51:36Z"
      message: 'load-balancer-api-internal: tcp connection to a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.346676ms
      message: 'load-balancer-api-internal: tcp connection to a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:21:36Z"
    - latency: 8.294566ms
      message: 'load-balancer-api-internal: resolved host name a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:21:36Z"
    - latency: 5.375622ms
      message: 'load-balancer-api-internal: tcp connection to a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:20:36Z"
    - latency: 9.678031ms
      message: 'load-balancer-api-internal: resolved host name a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:20:36Z"
    - latency: 5.013383ms
      message: 'load-balancer-api-internal: tcp connection to a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:19:36Z"
    - latency: 6.881304ms
      message: 'load-balancer-api-internal: resolved host name a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:19:36Z"
    - latency: 4.762824ms
      message: 'load-balancer-api-internal: tcp connection to a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:18:36Z"
    - latency: 6.952785ms
      message: 'load-balancer-api-internal: resolved host name a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:18:36Z"
    - latency: 5.810846ms
      message: 'load-balancer-api-internal: tcp connection to a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:17:36Z"
    - latency: 7.940002ms
      message: 'load-balancer-api-internal: resolved host name a4df53eb2fa0c478aa7cd9e727a5241c-6b20de1882da03ea.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:17:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T21:45:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-7-to-network-check-target-ip-10-0-129-67
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-7.ec2.internal
      uid: cbba0146-7c1b-438e-8d4b-13874e334160
    resourceVersion: "67017"
    uid: 052e3548-0a0c-440e-849a-3f16d4f5c075
  spec:
    sourcePod: network-check-source-7cbc45fddc-9vpfj
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:52:36Z"
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.39911ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:20:36Z"
    - latency: 2.366325ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:19:36Z"
    - latency: 2.343628ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:18:36Z"
    - latency: 2.671627ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:17:36Z"
    - latency: 2.221172ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:16:36Z"
    - latency: 2.814434ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:15:36Z"
    - latency: 2.683797ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:14:36Z"
    - latency: 2.403474ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:13:36Z"
    - latency: 2.589585ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:12:36Z"
    - latency: 2.946099ms
      message: 'network-check-target-ip-10-0-129-67: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:11:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T21:45:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-7-to-network-check-target-ip-10-0-131-170
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-7.ec2.internal
      uid: cbba0146-7c1b-438e-8d4b-13874e334160
    resourceVersion: "67018"
    uid: 4279224e-532d-4ee3-8116-49011e8fbba9
  spec:
    sourcePod: network-check-source-7cbc45fddc-9vpfj
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:52:36Z"
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.033991ms
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:20:36Z"
    - latency: 2.570103ms
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:19:36Z"
    - latency: 2.299335ms
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:18:36Z"
    - latency: 2.532356ms
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:17:36Z"
    - latency: 2.357715ms
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:16:36Z"
    - latency: 2.548043ms
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:15:36Z"
    - latency: 2.543497ms
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:14:36Z"
    - latency: 2.825623ms
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:13:36Z"
    - latency: 2.509027ms
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:12:36Z"
    - latency: 2.58095ms
      message: 'network-check-target-ip-10-0-131-170: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:11:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T21:45:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-7-to-network-check-target-ip-10-0-138-7
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-7.ec2.internal
      uid: cbba0146-7c1b-438e-8d4b-13874e334160
    resourceVersion: "67016"
    uid: 2a897cf9-4e28-4632-9959-bb19d4fe28c7
  spec:
    sourcePod: network-check-source-7cbc45fddc-9vpfj
    targetEndpoint: 10.132.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:52:36Z"
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 950.645µs
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:20:36Z"
    - latency: 989.351µs
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:19:36Z"
    - latency: 1.061703ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:18:36Z"
    - latency: 925.557µs
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:17:36Z"
    - latency: 1.062494ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:16:36Z"
    - latency: 858.133µs
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:15:36Z"
    - latency: 1.431011ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:14:36Z"
    - latency: 1.04919ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:13:36Z"
    - latency: 996.992µs
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:12:36Z"
    - latency: 1.476921ms
      message: 'network-check-target-ip-10-0-138-7: tcp connection to 10.132.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:11:36Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-09-17T21:45:35Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-138-7-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-138-7.ec2.internal
      uid: cbba0146-7c1b-438e-8d4b-13874e334160
    resourceVersion: "67472"
    uid: 548a9a90-9d00-46e7-81e3-43deecefda6c
  spec:
    sourcePod: network-check-source-7cbc45fddc-9vpfj
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-09-17T21:51:36Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 969.577µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:21:36Z"
    - latency: 1.861807ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:21:36Z"
    - latency: 1.132134ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:20:36Z"
    - latency: 1.839376ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:20:36Z"
    - latency: 974.271µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:19:36Z"
    - latency: 1.792271ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:19:36Z"
    - latency: 948.762µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:18:36Z"
    - latency: 1.730322ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:18:36Z"
    - latency: 1.148242ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-09-17T22:17:36Z"
    - latency: 1.86503ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-09-17T22:17:36Z"
kind: List
metadata:
  resourceVersion: ""