apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T20:41:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-118-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-118.ec2.internal
      uid: 20438abc-2940-430f-8e60-b49097e7942e
    resourceVersion: "55125"
    uid: 6bd1701a-141a-45ed-8a89-c006da5c721e
  spec:
    sourcePod: network-check-source-869dcfcdcd-zl86g
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T20:48:27Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.210649ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:16:27Z"
    - latency: 940.652µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:15:27Z"
    - latency: 864.765µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:14:27Z"
    - latency: 965.618µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:13:27Z"
    - latency: 931.029µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:12:27Z"
    - latency: 803.89µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:11:27Z"
    - latency: 997.032µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:10:27Z"
    - latency: 1.091538ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:09:27Z"
    - latency: 1.220483ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:08:27Z"
    - latency: 1.054846ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:07:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T20:41:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-118-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-118.ec2.internal
      uid: 20438abc-2940-430f-8e60-b49097e7942e
    resourceVersion: "56145"
    uid: db8f818e-6e09-4e41-a026-eacc87e7d483
  spec:
    sourcePod: network-check-source-869dcfcdcd-zl86g
    targetEndpoint: ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T20:47:27Z"
      message: 'load-balancer-api-external: tcp connection to ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.924995ms
      message: 'load-balancer-api-external: tcp connection to ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:17:27Z"
    - latency: 7.944602ms
      message: 'load-balancer-api-external: resolved host name ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:17:27Z"
    - latency: 4.083771ms
      message: 'load-balancer-api-external: tcp connection to ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:16:27Z"
    - latency: 8.268972ms
      message: 'load-balancer-api-external: resolved host name ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:16:27Z"
    - latency: 3.638414ms
      message: 'load-balancer-api-external: tcp connection to ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:15:27Z"
    - latency: 8.196641ms
      message: 'load-balancer-api-external: resolved host name ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:15:27Z"
    - latency: 4.02062ms
      message: 'load-balancer-api-external: tcp connection to ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:14:27Z"
    - latency: 8.515611ms
      message: 'load-balancer-api-external: resolved host name ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:14:27Z"
    - latency: 3.850636ms
      message: 'load-balancer-api-external: tcp connection to ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:13:27Z"
    - latency: 7.791601ms
      message: 'load-balancer-api-external: resolved host name ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:13:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T20:41:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-118-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-118.ec2.internal
      uid: 20438abc-2940-430f-8e60-b49097e7942e
    resourceVersion: "56144"
    uid: 867339d4-f47e-4aaa-9229-2bf73dc80ab5
  spec:
    sourcePod: network-check-source-869dcfcdcd-zl86g
    targetEndpoint: ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T20:47:27Z"
      message: 'load-balancer-api-internal: tcp connection to ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.714382ms
      message: 'load-balancer-api-internal: tcp connection to ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:17:27Z"
    - latency: 7.925563ms
      message: 'load-balancer-api-internal: resolved host name ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:17:27Z"
    - latency: 4.300849ms
      message: 'load-balancer-api-internal: tcp connection to ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:16:27Z"
    - latency: 8.191614ms
      message: 'load-balancer-api-internal: resolved host name ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:16:27Z"
    - latency: 3.64813ms
      message: 'load-balancer-api-internal: tcp connection to ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:15:27Z"
    - latency: 8.230144ms
      message: 'load-balancer-api-internal: resolved host name ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:15:27Z"
    - latency: 3.590061ms
      message: 'load-balancer-api-internal: tcp connection to ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:14:27Z"
    - latency: 8.459784ms
      message: 'load-balancer-api-internal: resolved host name ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:14:27Z"
    - latency: 3.793382ms
      message: 'load-balancer-api-internal: tcp connection to ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:13:27Z"
    - latency: 7.852361ms
      message: 'load-balancer-api-internal: resolved host name ab3355367900a426f9e4fedf910f5116-d3d9af7a01026d09.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:13:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T20:41:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-118-to-network-check-target-ip-10-0-137-185
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-118.ec2.internal
      uid: 20438abc-2940-430f-8e60-b49097e7942e
    resourceVersion: "55124"
    uid: 66504a5c-15a4-44ec-b8d0-7ceadc241a00
  spec:
    sourcePod: network-check-source-869dcfcdcd-zl86g
    targetEndpoint: 10.134.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T20:48:27Z"
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.587833ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:16:27Z"
    - latency: 2.478073ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:15:27Z"
    - latency: 2.240126ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:14:27Z"
    - latency: 2.348573ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:13:27Z"
    - latency: 2.925905ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:12:27Z"
    - latency: 2.20359ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:11:27Z"
    - latency: 2.523942ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:10:27Z"
    - latency: 2.588773ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:09:27Z"
    - latency: 2.058772ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:08:27Z"
    - latency: 2.202509ms
      message: 'network-check-target-ip-10-0-137-185: tcp connection to 10.134.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:07:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T20:41:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-118-to-network-check-target-ip-10-0-139-118
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-118.ec2.internal
      uid: 20438abc-2940-430f-8e60-b49097e7942e
    resourceVersion: "55122"
    uid: c9e138bf-f413-464d-8f25-6508710c45c1
  spec:
    sourcePod: network-check-source-869dcfcdcd-zl86g
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T20:48:27Z"
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.502367ms
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:16:27Z"
    - latency: 773.202µs
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:15:27Z"
    - latency: 703.754µs
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:14:27Z"
    - latency: 984.26µs
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:13:27Z"
    - latency: 1.109723ms
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:12:27Z"
    - latency: 871.273µs
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:11:27Z"
    - latency: 883.409µs
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:10:27Z"
    - latency: 871.593µs
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:09:27Z"
    - latency: 1.331049ms
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:08:27Z"
    - latency: 831.629µs
      message: 'network-check-target-ip-10-0-139-118: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:07:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T20:41:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-118-to-network-check-target-ip-10-0-139-64
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-118.ec2.internal
      uid: 20438abc-2940-430f-8e60-b49097e7942e
    resourceVersion: "55123"
    uid: 2d2a9b72-3459-4cd5-b3cc-9d76ac9af1ac
  spec:
    sourcePod: network-check-source-869dcfcdcd-zl86g
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T20:48:27Z"
      message: 'network-check-target-ip-10-0-139-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.612366ms
      message: 'network-check-target-ip-10-0-139-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:16:27Z"
    - latency: 2.658867ms
      message: 'network-check-target-ip-10-0-139-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:15:27Z"
    - latency: 2.480507ms
      message: 'network-check-target-ip-10-0-139-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:14:27Z"
    - latency: 2.000827ms
      message: 'network-check-target-ip-10-0-139-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:13:27Z"
    - latency: 2.250988ms
      message: 'network-check-target-ip-10-0-139-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:12:27Z"
    - latency: 2.010686ms
      message: 'network-check-target-ip-10-0-139-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:11:27Z"
    - latency: 2.286906ms
      message: 'network-check-target-ip-10-0-139-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:10:27Z"
    - latency: 2.1326ms
      message: 'network-check-target-ip-10-0-139-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:09:27Z"
    - latency: 1.962649ms
      message: 'network-check-target-ip-10-0-139-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:08:27Z"
    - latency: 2.494934ms
      message: 'network-check-target-ip-10-0-139-64: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:07:27Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-10T20:41:26Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-139-118-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-139-118.ec2.internal
      uid: 20438abc-2940-430f-8e60-b49097e7942e
    resourceVersion: "56143"
    uid: 5162b6fc-148d-4451-8642-1c4787b3170b
  spec:
    sourcePod: network-check-source-869dcfcdcd-zl86g
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-10T20:47:27Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 862.231µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:17:27Z"
    - latency: 1.665105ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:17:27Z"
    - latency: 979.886µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:16:27Z"
    - latency: 1.712657ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:16:27Z"
    - latency: 677.326µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:15:27Z"
    - latency: 1.652599ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:15:27Z"
    - latency: 1.233224ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:14:27Z"
    - latency: 1.908732ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:14:27Z"
    - latency: 809.565µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-10T21:13:27Z"
    - latency: 1.733395ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-10T21:13:27Z"
kind: List
metadata:
  resourceVersion: ""