apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:22:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-255-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-255.ec2.internal
      uid: 1692331e-75f8-483d-a9e5-716767b0567d
    resourceVersion: "61519"
    uid: 5d626360-b2eb-4baa-8a38-8fc4d539339e
  spec:
    sourcePod: network-check-source-869dcfcdcd-6hbzr
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:29:28Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.462085ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:04:28Z"
    - latency: 1.24084ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:03:28Z"
    - latency: 1.178338ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:02:28Z"
    - latency: 1.070195ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:01:28Z"
    - latency: 970.358µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:00:28Z"
    - latency: 874.116µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:59:28Z"
    - latency: 1.09121ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:58:28Z"
    - latency: 1.137667ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:57:28Z"
    - latency: 1.033205ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:56:28Z"
    - latency: 3.829578ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:55:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:22:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-255-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-255.ec2.internal
      uid: 1692331e-75f8-483d-a9e5-716767b0567d
    resourceVersion: "61520"
    uid: 78b8fc52-9baf-4eb3-95c9-b6329c19b9d0
  spec:
    sourcePod: network-check-source-869dcfcdcd-6hbzr
    targetEndpoint: a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:28:28Z"
      message: 'load-balancer-api-external: tcp connection to a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 4.322125ms
      message: 'load-balancer-api-external: tcp connection to a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:04:28Z"
    - latency: 8.026058ms
      message: 'load-balancer-api-external: resolved host name a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:04:28Z"
    - latency: 4.304643ms
      message: 'load-balancer-api-external: tcp connection to a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:03:28Z"
    - latency: 8.259555ms
      message: 'load-balancer-api-external: resolved host name a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:03:28Z"
    - latency: 5.381133ms
      message: 'load-balancer-api-external: tcp connection to a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:02:28Z"
    - latency: 7.927925ms
      message: 'load-balancer-api-external: resolved host name a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:02:28Z"
    - latency: 5.19911ms
      message: 'load-balancer-api-external: tcp connection to a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:01:28Z"
    - latency: 8.831123ms
      message: 'load-balancer-api-external: resolved host name a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:01:28Z"
    - latency: 4.705728ms
      message: 'load-balancer-api-external: tcp connection to a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:00:28Z"
    - latency: 9.516111ms
      message: 'load-balancer-api-external: resolved host name a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:00:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:22:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-255-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-255.ec2.internal
      uid: 1692331e-75f8-483d-a9e5-716767b0567d
    resourceVersion: "61521"
    uid: e9632dd2-5dfb-4fd3-bd36-41154f186adf
  spec:
    sourcePod: network-check-source-869dcfcdcd-6hbzr
    targetEndpoint: a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:28:28Z"
      message: 'load-balancer-api-internal: tcp connection to a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.188567ms
      message: 'load-balancer-api-internal: tcp connection to a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:04:28Z"
    - latency: 7.928298ms
      message: 'load-balancer-api-internal: resolved host name a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:04:28Z"
    - latency: 4.34729ms
      message: 'load-balancer-api-internal: tcp connection to a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:03:28Z"
    - latency: 8.325359ms
      message: 'load-balancer-api-internal: resolved host name a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:03:28Z"
    - latency: 4.415912ms
      message: 'load-balancer-api-internal: tcp connection to a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:02:28Z"
    - latency: 7.882369ms
      message: 'load-balancer-api-internal: resolved host name a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:02:28Z"
    - latency: 4.100288ms
      message: 'load-balancer-api-internal: tcp connection to a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:01:28Z"
    - latency: 8.796183ms
      message: 'load-balancer-api-internal: resolved host name a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:01:28Z"
    - latency: 4.72254ms
      message: 'load-balancer-api-internal: tcp connection to a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:00:28Z"
    - latency: 9.444317ms
      message: 'load-balancer-api-internal: resolved host name a9cd2526d72a64635a5cb8e193b699ac-67ecc6d5b158433e.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:00:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:22:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-255-to-network-check-target-ip-10-0-133-87
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-255.ec2.internal
      uid: 1692331e-75f8-483d-a9e5-716767b0567d
    resourceVersion: "61518"
    uid: 991257a8-9d52-4d6d-84a5-255d57eb3e4a
  spec:
    sourcePod: network-check-source-869dcfcdcd-6hbzr
    targetEndpoint: 10.133.0.4:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:29:28Z"
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.305171ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:04:28Z"
    - latency: 1.918194ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:03:28Z"
    - latency: 1.968332ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:02:28Z"
    - latency: 1.95775ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:01:28Z"
    - latency: 2.196165ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:00:28Z"
    - latency: 2.097411ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:59:28Z"
    - latency: 2.180236ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:58:28Z"
    - latency: 2.525299ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:57:28Z"
    - latency: 2.145592ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:56:28Z"
    - latency: 3.063684ms
      message: 'network-check-target-ip-10-0-133-87: tcp connection to 10.133.0.4:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:55:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:22:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-255-to-network-check-target-ip-10-0-136-255
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-255.ec2.internal
      uid: 1692331e-75f8-483d-a9e5-716767b0567d
    resourceVersion: "61515"
    uid: 208e9fa5-71a9-45b0-a2fd-7c298b4244fa
  spec:
    sourcePod: network-check-source-869dcfcdcd-6hbzr
    targetEndpoint: 10.132.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:29:28Z"
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.072824ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:04:28Z"
    - latency: 924.697µs
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:03:28Z"
    - latency: 969.754µs
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:02:28Z"
    - latency: 891.296µs
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:01:28Z"
    - latency: 1.416177ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:00:28Z"
    - latency: 1.109476ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:59:28Z"
    - latency: 854.814µs
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:58:28Z"
    - latency: 1.218384ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:57:28Z"
    - latency: 933.967µs
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:56:28Z"
    - latency: 4.433094ms
      message: 'network-check-target-ip-10-0-136-255: tcp connection to 10.132.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:55:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:22:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-255-to-network-check-target-ip-10-0-142-172
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-255.ec2.internal
      uid: 1692331e-75f8-483d-a9e5-716767b0567d
    resourceVersion: "61516"
    uid: 8eebafef-0bc7-4906-81ca-93445c5369c9
  spec:
    sourcePod: network-check-source-869dcfcdcd-6hbzr
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:29:28Z"
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.161597ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:04:28Z"
    - latency: 2.343737ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:03:28Z"
    - latency: 2.531311ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:02:28Z"
    - latency: 2.496331ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:01:28Z"
    - latency: 2.134993ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:00:28Z"
    - latency: 2.547393ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:59:28Z"
    - latency: 2.360736ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:58:28Z"
    - latency: 2.573896ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:57:28Z"
    - latency: 2.730301ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:56:28Z"
    - latency: 3.306126ms
      message: 'network-check-target-ip-10-0-142-172: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T11:55:28Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-14T11:22:27Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-136-255-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-136-255.ec2.internal
      uid: 1692331e-75f8-483d-a9e5-716767b0567d
    resourceVersion: "61517"
    uid: 0bf1de4e-8f70-4eeb-8187-1b6b65317ad4
  spec:
    sourcePod: network-check-source-869dcfcdcd-6hbzr
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-14T11:28:28Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 891.881µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:04:28Z"
    - latency: 2.068443ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:04:28Z"
    - latency: 905.24µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:03:28Z"
    - latency: 1.798259ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:03:28Z"
    - latency: 935.831µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:02:28Z"
    - latency: 1.739932ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:02:28Z"
    - latency: 1.367925ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:01:28Z"
    - latency: 1.998934ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:01:28Z"
    - latency: 916.609µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-14T12:00:28Z"
    - latency: 2.085939ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-14T12:00:28Z"
kind: List
metadata:
  resourceVersion: ""