apiVersion: v1
items:
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T09:15:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-99-to-kubernetes-default-service-cluster-0
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-99.ec2.internal
      uid: f08d08a5-1b63-4c90-a2b8-628d485572b4
    resourceVersion: "48518"
    uid: 8758a226-8ab2-4475-948b-2dd651c9c50b
  spec:
    sourcePod: network-check-source-869dcfcdcd-f9wzl
    targetEndpoint: 172.31.0.1:443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T09:22:07Z"
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 884.842µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:43:07Z"
    - latency: 1.218712ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:42:07Z"
    - latency: 1.244553ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:41:07Z"
    - latency: 1.336431ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:40:07Z"
    - latency: 5.955968ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:39:07Z"
    - latency: 1.478487ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:38:07Z"
    - latency: 857.44µs
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:37:07Z"
    - latency: 1.14805ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:36:07Z"
    - latency: 1.311831ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:35:07Z"
    - latency: 1.125857ms
      message: 'kubernetes-default-service-cluster-0: tcp connection to 172.31.0.1:443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:34:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T09:15:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-99-to-load-balancer-api-external
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-99.ec2.internal
      uid: f08d08a5-1b63-4c90-a2b8-628d485572b4
    resourceVersion: "51366"
    uid: c61dfbfa-120b-48f5-8c59-2126d6449ad2
  spec:
    sourcePod: network-check-source-869dcfcdcd-f9wzl
    targetEndpoint: a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T09:21:07Z"
      message: 'load-balancer-api-external: tcp connection to a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 5.037168ms
      message: 'load-balancer-api-external: tcp connection to a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:45:07Z"
    - latency: 33.01787ms
      message: 'load-balancer-api-external: resolved host name a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:45:07Z"
    - latency: 4.863576ms
      message: 'load-balancer-api-external: tcp connection to a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:44:07Z"
    - latency: 7.086604ms
      message: 'load-balancer-api-external: resolved host name a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:44:07Z"
    - latency: 7.564024ms
      message: 'load-balancer-api-external: tcp connection to a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:43:07Z"
    - latency: 7.389993ms
      message: 'load-balancer-api-external: resolved host name a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:43:07Z"
    - latency: 4.952012ms
      message: 'load-balancer-api-external: tcp connection to a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:42:07Z"
    - latency: 7.403644ms
      message: 'load-balancer-api-external: resolved host name a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:42:07Z"
    - latency: 5.082798ms
      message: 'load-balancer-api-external: tcp connection to a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:41:07Z"
    - latency: 8.826956ms
      message: 'load-balancer-api-external: resolved host name a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:41:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T09:15:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-99-to-load-balancer-api-internal
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-99.ec2.internal
      uid: f08d08a5-1b63-4c90-a2b8-628d485572b4
    resourceVersion: "51365"
    uid: e5784a4c-80dd-47a2-97a0-ca4f01a7d454
  spec:
    sourcePod: network-check-source-869dcfcdcd-f9wzl
    targetEndpoint: a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com:6443
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T09:21:07Z"
      message: 'load-balancer-api-internal: tcp connection to a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 6.928517ms
      message: 'load-balancer-api-internal: tcp connection to a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:45:07Z"
    - latency: 16.203452ms
      message: 'load-balancer-api-internal: resolved host name a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:45:07Z"
    - latency: 5.312741ms
      message: 'load-balancer-api-internal: tcp connection to a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:44:07Z"
    - latency: 7.014354ms
      message: 'load-balancer-api-internal: resolved host name a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:44:07Z"
    - latency: 4.735674ms
      message: 'load-balancer-api-internal: tcp connection to a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:43:07Z"
    - latency: 7.328446ms
      message: 'load-balancer-api-internal: resolved host name a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:43:07Z"
    - latency: 6.432446ms
      message: 'load-balancer-api-internal: tcp connection to a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:42:07Z"
    - latency: 7.368224ms
      message: 'load-balancer-api-internal: resolved host name a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:42:07Z"
    - latency: 5.094728ms
      message: 'load-balancer-api-internal: tcp connection to a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com:6443
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:41:07Z"
    - latency: 8.741408ms
      message: 'load-balancer-api-internal: resolved host name a72b257fbe87f4c5da480521dc4a08ad-7bdc6b0691d5f4a0.elb.us-east-1.amazonaws.com
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:41:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T09:15:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-99-to-network-check-target-ip-10-0-129-99
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-99.ec2.internal
      uid: f08d08a5-1b63-4c90-a2b8-628d485572b4
    resourceVersion: "48515"
    uid: ad55b0ea-c1a9-4f07-9e84-f665fe1ac351
  spec:
    sourcePod: network-check-source-869dcfcdcd-f9wzl
    targetEndpoint: 10.133.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T09:22:07Z"
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 1.083319ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:43:07Z"
    - latency: 1.403778ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:42:07Z"
    - latency: 1.10375ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:41:07Z"
    - latency: 1.497031ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:40:07Z"
    - latency: 3.209663ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:39:07Z"
    - latency: 832.488µs
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:38:07Z"
    - latency: 1.092795ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:37:07Z"
    - latency: 1.177016ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:36:07Z"
    - latency: 1.283373ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:35:07Z"
    - latency: 1.311718ms
      message: 'network-check-target-ip-10-0-129-99: tcp connection to 10.133.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:34:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T09:15:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-99-to-network-check-target-ip-10-0-138-144
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-99.ec2.internal
      uid: f08d08a5-1b63-4c90-a2b8-628d485572b4
    resourceVersion: "48516"
    uid: c0badad0-2ba8-4c8d-a57e-95c16dc5bdd8
  spec:
    sourcePod: network-check-source-869dcfcdcd-f9wzl
    targetEndpoint: 10.134.0.3:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T09:22:07Z"
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.333239ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:43:07Z"
    - latency: 2.250867ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:42:07Z"
    - latency: 2.098161ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:41:07Z"
    - latency: 2.160816ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:40:07Z"
    - latency: 4.475045ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:39:07Z"
    - latency: 2.351157ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:38:07Z"
    - latency: 2.072716ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:37:07Z"
    - latency: 2.305738ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:36:07Z"
    - latency: 2.221569ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:35:07Z"
    - latency: 2.15635ms
      message: 'network-check-target-ip-10-0-138-144: tcp connection to 10.134.0.3:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:34:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T09:15:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-99-to-network-check-target-ip-10-0-138-89
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-99.ec2.internal
      uid: f08d08a5-1b63-4c90-a2b8-628d485572b4
    resourceVersion: "48517"
    uid: 80588d67-6e87-4a9e-b752-0a4c8fd696ed
  spec:
    sourcePod: network-check-source-869dcfcdcd-f9wzl
    targetEndpoint: 10.132.0.5:8080
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T09:22:07Z"
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 2.042994ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:43:07Z"
    - latency: 1.911667ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:42:07Z"
    - latency: 1.918709ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:41:07Z"
    - latency: 1.813092ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:40:07Z"
    - latency: 1.872977ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:39:07Z"
    - latency: 1.934797ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:38:07Z"
    - latency: 2.093202ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:37:07Z"
    - latency: 1.992038ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:36:07Z"
    - latency: 1.995636ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:35:07Z"
    - latency: 1.841153ms
      message: 'network-check-target-ip-10-0-138-89: tcp connection to 10.132.0.5:8080
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:34:07Z"
- apiVersion: controlplane.operator.openshift.io/v1alpha1
  kind: PodNetworkConnectivityCheck
  metadata:
    creationTimestamp: "2026-07-13T09:15:06Z"
    generation: 1
    labels:
      networking.openshift.io/managedBy: oc-connectivity-check-controller
    name: network-check-source-ip-10-0-129-99-to-network-check-target-service-cluster
    namespace: openshift-network-diagnostics
    ownerReferences:
    - apiVersion: v1
      kind: Node
      name: ip-10-0-129-99.ec2.internal
      uid: f08d08a5-1b63-4c90-a2b8-628d485572b4
    resourceVersion: "51364"
    uid: b7f6f8f2-97b7-4d19-87ed-b88ced2a0120
  spec:
    sourcePod: network-check-source-869dcfcdcd-f9wzl
    targetEndpoint: network-check-target:80
  status:
    conditions:
    - lastTransitionTime: "2026-07-13T09:21:07Z"
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnectSuccess
      status: "True"
      type: Reachable
    successes:
    - latency: 3.488496ms
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:45:07Z"
    - latency: 5.475751ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:45:07Z"
    - latency: 904.577µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:44:07Z"
    - latency: 1.785361ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:44:07Z"
    - latency: 987.343µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:43:07Z"
    - latency: 2.204248ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:43:07Z"
    - latency: 866.432µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:42:07Z"
    - latency: 1.842655ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:42:07Z"
    - latency: 909.553µs
      message: 'network-check-target-service-cluster: tcp connection to network-check-target:80
        succeeded'
      reason: TCPConnect
      success: true
      time: "2026-07-13T09:41:07Z"
    - latency: 2.02851ms
      message: 'network-check-target-service-cluster: resolved host name network-check-target
        successfully'
      reason: DNSResolve
      success: true
      time: "2026-07-13T09:41:07Z"
kind: List
metadata:
  resourceVersion: ""