Configure PD DigitalOcean Kubernetes checkout options in WHMCS
Offer the cluster dimensions your customers should choose while keeping other values fixed in the product’s module settings. Native configurable-option generation is supported for this platform.
Generate the intended group
- Save the product with its intended provider account, region, version, node plan and worker-count defaults.
- Open PD Modules → DigitalOcean Kubernetes → Products and find that product.
- Choose Generate options if there is no generated group. If the action says Rebuild from live catalog, review the price-reset warning first.
- Inspect all four generated dimensions: Region, Kubernetes version, Node plan and Worker nodes. The default visible set omits Kubernetes version; that does not mean the dimension is absent.
- Review and edit the attached group’s prices under System Settings → Products/Services → Configurable Options. Preview the actual order form before making the offering available.
Worker nodes is a quantity from 1–10. A listed plan or version is not a capacity test for every account and region: the catalogue may be cached or supplied by a fallback list.
Set visibility separately
Expand Customer-selectable dimensions, tick the dimensions customers should choose and use Save visibility. Hidden dimensions are intended to use the product’s saved module defaults. Inspect the saved group and preview checkout afterwards rather than relying only on the result message.
Saving visibility is different from rebuilding. Recheck the fixed plan, count and version whenever you stop exposing those choices to customers. Do not treat a version choice for new orders as a Kubernetes version-upgrade control for an existing cluster.
Review prices and optional margin
Without a saved margin, generated choices start with zero prices for you to review and edit. Save margin stores a percentage but changes no existing price by itself. Generate or Rebuild can use it where the panel can suggest prices, or refuse when the chosen combination or required cost/currency information cannot be priced.
Review every billing term and currency you offer, and read any refusal before proceeding. A cost estimate is not the final provider bill: control-plane options, load balancers, storage and other workload resources need their own cost review. Do not assume every provider charge is included in the worker-node estimate.
Rebuild deliberately
The reviewed native option stores reuse compatible choice identities, but rebuilding resets prices to newly generated values. Record your customised choices and prices before rebuilding an existing offering. Use the visibility-only operation when that is all you need to change.
If the result is uncertain, inspect the existing linked group before another Generate or Rebuild. Do not send tokens or customer billing information.
See the PD DigitalOcean Kubernetes WHMCS guide for related setup, or explore PD DigitalOcean Kubernetes.