Skip to documentation content
Cloud documentationCloud statusPilot in preparation
On this page
Get started

Manage a cluster in the Cloud

Plan capacity, request a managed cluster and follow create, scale, upgrade and removal states in one authenticated browser workspace.

GuideCloud conceptReading time · approx.8 minutesUpdated
Availability of this guideCloud concept

These steps describe the intended customer path. Use the interface only after personal access and written confirmation of this capability in your pilot scope.

Before you start

Bring an approved workspace, the intended workload size and the individual pilot scope. You do not need a provider account, provider API key, kubeconfig or local Kubernetes client.

1. Request the right capacity

Start in Clusters and describe the workload, environments, node count, storage growth and recovery expectations. The browser should show the selected plan limit and the infrastructure items that are priced separately.

ReviewWhy it matters
Plan and workspaceThe plan controls management limits; it does not include unlimited machines.
Compute, storage and networkThese resources are added to the platform fee and require a confirmed configuration.
Kubernetes version and change windowLifecycle support and maintenance depend on the qualified pilot scope.

2. Create and observe

  1. 01

    Review the quote

    Confirm the immutable quote, recurring platform fee, infrastructure items, tax treatment and approval step before requesting paid capacity.

  2. 02

    Submit from the browser

    The Cloud service records the request and returns an operation ID. A click or redirect alone does not mean that a cluster exists.

  3. 03

    Wait for observed readiness

    Follow provisioning, validation and readiness in the same workspace. Unknown or delayed status is surfaced instead of being shown as healthy.

3. Scale and upgrade deliberately

Use the cluster action menu for a change. The page must show the current capacity, the requested delta, expected cost effect, maintenance window and rollback or recovery boundary before confirmation.

4. Export and remove safely

Before removal, review application revisions, data retention, export responsibilities and the end-of-pilot decision in the browser. Removal is a separate confirmation and must not be inferred from a failed or expired operation.

Migrate workloads & plan an exit → · Understand pricing & usage → · Get useful support quickly →

Use this guide within your agreed pilot scope. Kubernetes examples are not evidence of a generally available Cloud capability.