Use the service’s node view to inspect the provider-reported pools and worker states. Compare it with the cluster overview when checking initial provisioning or an authorised plan change.

Read the cluster and node views

1. Open the service’s Information tab in the Blesta client area and note the cluster state, region, version and worker summary.
2. Open Nodes on the service’s tab list.
3. Review each displayed pool’s name, node plan and count, then the names and states of its worker nodes.
4. If a change was requested, compare these details with the intended plan/count and the recent Activity outcome before deciding it finished.

The overview’s summary can come from the module’s saved service record, while the Nodes view requests the provider’s pool information. A short-lived difference during a change is a reason to check progress, not proof that the order or pool has vanished.

Interpret an empty list or healthy-looking state

If the node list is empty, check activation and cluster state first, then review provider connectivity and permissions. A failed provider read can also produce an empty list. Do not conclude that there are zero billable nodes or that the cluster was deleted from this page alone.

A running cluster or worker status does not establish that your applications are healthy. Workload scheduling, readiness, resource requests and application errors need checking through your normal Kubernetes administration process. The module’s Nodes page is a status view; it is not a full workload dashboard.

Choose the next action

For an initial cluster still provisioning, inspect Activity, normal cron progress and the provider outcome. For a recently requested worker-plan or count change, wait for the intended result rather than starting another overlapping change.

The reviewed client panel does not provide add/delete/edit node-pool buttons. Use your supported service-change process for an authorised plan change; establish how provider-side alterations affect the tracked service before making them.

Do not include kubeconfig, API tokens, private workload data or full customer records.

See the PD DigitalOcean Kubernetes Blesta guide for related setup, or explore PD DigitalOcean Kubernetes.