apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:32:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-117-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-117.us-east-2.compute.internal
      uid: 645227a7-0092-4098-86e0-afd45b59b2fb
    resourceVersion: "26718"
    uid: 74fd2831-06f6-4a0f-8966-071c00882ed6
  spec:
    sourcePod: network-check-source-6f78d59f99-khm6r
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:39:26Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.245568ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:46:26Z"
    - latency: 1.459999ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:45:26Z"
    - latency: 1.061853ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:44:26Z"
    - latency: 1.09796ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:43:26Z"
    - latency: 1.658088ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:42:26Z"
    - latency: 1.111691ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:41:26Z"
    - latency: 1.086601ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:40:26Z"
    - latency: 1.44273ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:39:26Z"
    - latency: 1.008622ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:38:26Z"
    - latency: 1.096336ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:37:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:32:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-117-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-117.us-east-2.compute.internal
      uid: 645227a7-0092-4098-86e0-afd45b59b2fb
    resourceVersion: "36163"
    uid: 1c570e67-43f0-4b79-9da9-d5635e8c0fcb
  spec:
    sourcePod: network-check-source-6f78d59f99-khm6r
    targetEndpoint: af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:38:26Z"
      message: 'load-balancer-api-external: tcp connection to af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.104893ms
      message: 'load-balancer-api-external: tcp connection to af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:50:26Z"
    - latency: 9.305283ms
      message: 'load-balancer-api-external: resolved host name af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:50:26Z"
    - latency: 5.557936ms
      message: 'load-balancer-api-external: tcp connection to af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:49:26Z"
    - latency: 9.926018ms
      message: 'load-balancer-api-external: resolved host name af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:49:26Z"
    - latency: 6.011909ms
      message: 'load-balancer-api-external: tcp connection to af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:48:26Z"
    - latency: 8.187676ms
      message: 'load-balancer-api-external: resolved host name af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:48:26Z"
    - latency: 6.995926ms
      message: 'load-balancer-api-external: tcp connection to af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:47:26Z"
    - latency: 7.818728ms
      message: 'load-balancer-api-external: resolved host name af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:47:26Z"
    - latency: 6.129737ms
      message: 'load-balancer-api-external: tcp connection to af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:46:26Z"
    - latency: 6.917378ms
      message: 'load-balancer-api-external: resolved host name af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:46:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:32:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-117-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-117.us-east-2.compute.internal
      uid: 645227a7-0092-4098-86e0-afd45b59b2fb
    resourceVersion: "36162"
    uid: 917637f3-e937-420f-b5d9-81908acf7058
  spec:
    sourcePod: network-check-source-6f78d59f99-khm6r
    targetEndpoint: af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:38:26Z"
      message: 'load-balancer-api-internal: tcp connection to af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.119534ms
      message: 'load-balancer-api-internal: tcp connection to af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:50:26Z"
    - latency: 9.139423ms
      message: 'load-balancer-api-internal: resolved host name af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:50:26Z"
    - latency: 5.587605ms
      message: 'load-balancer-api-internal: tcp connection to af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:49:26Z"
    - latency: 9.963189ms
      message: 'load-balancer-api-internal: resolved host name af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:49:26Z"
    - latency: 5.888184ms
      message: 'load-balancer-api-internal: tcp connection to af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:48:26Z"
    - latency: 8.100386ms
      message: 'load-balancer-api-internal: resolved host name af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:48:26Z"
    - latency: 7.222852ms
      message: 'load-balancer-api-internal: tcp connection to af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:47:26Z"
    - latency: 8.008939ms
      message: 'load-balancer-api-internal: resolved host name af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:47:26Z"
    - latency: 6.142834ms
      message: 'load-balancer-api-internal: tcp connection to af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:46:26Z"
    - latency: 6.851057ms
      message: 'load-balancer-api-internal: resolved host name af8751b22896f4eb1936422622bc94ff-6cc5c3b86e3f8a16.elb.us-east-2.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:46:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:32:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-117-to-network-check-target-ip-10-0-130-81
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-117.us-east-2.compute.internal
      uid: 645227a7-0092-4098-86e0-afd45b59b2fb
    resourceVersion: "26716"
    uid: 0ba8369c-0f50-4721-8040-1c7f583bffd8
  spec:
    sourcePod: network-check-source-6f78d59f99-khm6r
    targetEndpoint: 10.134.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:39:26Z"
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.48372ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:46:26Z"
    - latency: 2.206164ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:45:26Z"
    - latency: 2.529536ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:44:26Z"
    - latency: 2.287579ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:43:26Z"
    - latency: 2.110393ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:42:26Z"
    - latency: 2.305216ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:41:26Z"
    - latency: 2.098096ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:40:26Z"
    - latency: 2.269608ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:39:26Z"
    - latency: 2.362034ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:38:26Z"
    - latency: 1.941489ms
      message: 'network-check-target-ip-10-0-130-81: tcp connection to 10.134.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:37:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:32:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-117-to-network-check-target-ip-10-0-133-117
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-117.us-east-2.compute.internal
      uid: 645227a7-0092-4098-86e0-afd45b59b2fb
    resourceVersion: "26715"
    uid: cde4df7b-bf19-4d8c-96a0-a5cdf323313e
  spec:
    sourcePod: network-check-source-6f78d59f99-khm6r
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:39:26Z"
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.445337ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:46:26Z"
    - latency: 2.170435ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:45:26Z"
    - latency: 1.490502ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:44:26Z"
    - latency: 1.695345ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:43:26Z"
    - latency: 936.493µs
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:42:26Z"
    - latency: 1.341776ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:41:26Z"
    - latency: 783.979µs
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:40:26Z"
    - latency: 1.49954ms
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:39:26Z"
    - latency: 810.981µs
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:38:26Z"
    - latency: 908.635µs
      message: 'network-check-target-ip-10-0-133-117: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:37:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:32:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-117-to-network-check-target-ip-10-0-141-130
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-117.us-east-2.compute.internal
      uid: 645227a7-0092-4098-86e0-afd45b59b2fb
    resourceVersion: "26717"
    uid: 0d131575-a964-4c25-96cc-969ac51d8267
  spec:
    sourcePod: network-check-source-6f78d59f99-khm6r
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:39:26Z"
      message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.288352ms
      message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:46:26Z"
    - latency: 2.358664ms
      message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:45:26Z"
    - latency: 2.098181ms
      message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:44:26Z"
    - latency: 2.321418ms
      message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:43:26Z"
    - latency: 2.144906ms
      message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:42:26Z"
    - latency: 2.287167ms
      message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:41:26Z"
    - latency: 1.755128ms
      message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:40:26Z"
    - latency: 2.127356ms
      message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:39:26Z"
    - latency: 2.007936ms
      message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:38:26Z"
    - latency: 2.019827ms
      message: 'network-check-target-ip-10-0-141-130: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:37:26Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-11-03T17:32:25Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-133-117-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-133-117.us-east-2.compute.internal
      uid: 645227a7-0092-4098-86e0-afd45b59b2fb
    resourceVersion: "36158"
    uid: b3f11b2c-fba8-4606-9250-f8831c5db1ae
  spec:
    sourcePod: network-check-source-6f78d59f99-khm6r
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-11-03T17:38:26Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.467867ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:50:26Z"
    - latency: 1.812585ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:50:26Z"
    - latency: 1.201883ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:49:26Z"
    - latency: 1.956145ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:49:26Z"
    - latency: 984.49µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:48:26Z"
    - latency: 1.743139ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:48:26Z"
    - latency: 1.136271ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:47:26Z"
    - latency: 2.379421ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:47:26Z"
    - latency: 1.070276ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-11-03T17:46:26Z"
    - latency: 1.853374ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-11-03T17:46:26Z"
kind: List
metadata:
  resourceVersion: ""