On this page
Upgrade Kubernetes safely
Prepare, preflight and follow a Kubernetes version upgrade in the web interface, including compatibility, maintenance and recovery checks.
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
Before opening Update, name the application owner, confirm a tested release, check data protection evidence, identify API compatibility and reserve a maintenance window. Keep an approved recovery decision available; a version downgrade must not be assumed.
1. Prepare the change
- ✓Record current Kubernetes version, add-ons, workload revisions and the intended target.
- ✓Confirm that the target is supported for the cluster topology and pilot scope.
- ✓Test application and API compatibility, including admission policies, ingress, storage and identity paths.
- ✓Agree maintenance window, communication, acceptance test and recovery owner.
2. Run the browser preflight
- 01
Open Update → Start
Select the target cluster and review the current observed version. The page must show your organization, cluster and authorization scope.
- 02
Choose the release target
Select only a target approved for your pilot. Read the compatibility, release notes and maintenance impact presented by the service.
- 03
Pass readiness gates
Review backup readiness, capacity headroom, disruption checks and blocked resources. A gate that cannot be verified blocks a safe start.
- 04
Confirm the window
Confirm only after owners and recovery decisions are recorded. The service returns an operation ID; it does not turn the page into a live terminal.
3. Observe and accept
| State | What to do |
|---|---|
| Preflight / queued | Read the remaining gate; do not start another upgrade. |
| Running | Follow release phases and watch the agreed application smoke test. |
| Succeeded | Verify version, nodes, add-ons, workloads and user journey; record evidence. |
| Failed / unknown | Preserve operation ID, read reason and escalate; do not infer recovery from a refreshed page. |
4. If compatibility breaks
Use the application recovery plan: restore a known-good application revision, recover data through the agreed protection service or pause the rollout with support. Do not promise that Kubernetes can be downgraded safely. Share the operation ID, target version, last successful check and redacted error.
Backups and recovery in the portal → · Get useful support quickly →
Use this guide within your agreed pilot scope. Kubernetes examples are not evidence of a generally available Cloud capability.