Define a managed-cluster offering with its intended region, Kubernetes version, worker-node plan and node count. The module creates a cluster with an initial worker pool when the service is intentionally activated.

Create the offering

1. Open Packages → Packages → Add Package.
2. Choose PD DigitalOcean Kubernetes as the module and select the intended saved DigitalOcean account.
3. Review Region, Version, Node plan and Nodes in the module options.
4. Review Resource name prefix, optional Project and Client: Kubeconfig download. Set your package terms and pricing, choose its package group and save.
5. Add that package group to the intended order form under Packages → Order Forms when the offering is ready.

Review Hold paid pending services for manual activation and the Provision Paid Pending Services automation task. Leave the hold unticked if eligible paid orders should activate automatically, and keep the normal cron running. Payment and a saved package are not proof that a cluster is running.

Choose the cluster defaults

Choose from this module’s Kubernetes lists rather than assuming every standalone Droplet size is a supported worker plan. The module’s starting worker count is limited to 1–10. Confirm the selected plan is supported in the intended region and that your account has the capacity required for the offering.

The catalogue can be cached or use shipped fallback choices when DigitalOcean cannot be reached. A listed combination is not a live deployment test for your account. Latest is a provider-resolved version choice for creating a cluster; choosing it does not turn this product field into an automatic upgrade policy for existing clusters.

Project is optional organisational grouping. The background process attempts it after the cluster is running; a ready cluster does not prove that project assignment succeeded.

Review checkout and customer access

Use PD Modules → DigitalOcean Kubernetes → Products to generate and review Region, Kubernetes version, Node plan and Worker nodes. Decide which dimensions customers can select and inspect the actual selected values, terms and prices before opening sales.

Enable Client: Kubeconfig download deliberately if customers should administer their clusters. The file contains cluster-access credentials; it is different from the host’s DigitalOcean API token. Keep provider tokens and credentials out of the optional Client Area Section text.

Verify the intended activation

When ready, use your normal authorised provisioning test. A real activation creates chargeable provider resources. Review Clients & Clusters, the service state, API endpoint and Activity, and keep the normal cron running for background progress.

A completed order or Ready options label is not proof that Kubernetes is running. Once available, check the node information and intended client access separately; cluster readiness alone does not establish that a workload is healthy. Resolve an uncertain earlier create result before repeating activation. Keep tokens, kubeconfig and customer data out of shared screenshots.

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