Deckhouse Platform (DP) includes a built-in update management mechanism for both the platform itself and Kubernetes cluster components. To roll out new versions consistently and safely, DP uses a five-channel update system ranging from the newest and unstable (Alpha) to the most thoroughly tested (Rock Solid). Each new version gradually moves through these channels, helping identify issues early and ensuring stability in production environments. For details on each channel, refer to the Architecture section.
DP does not support version downgrades. After a release is installed, rolling the platform back to an earlier minor or patch version is not possible.
When switching to a more stable channel, the platform remains on the current release until a newer version becomes available on that channel.
Rolling back by one minor version is possible only for the Kubernetes (control plane) version, not for the DP version.
You can configure the update process. Both automatic and manual modes are supported, as well as update windows and other parameters. See Update configuration for details.
An alerting system is used to track the update status and quickly report any issues. For more information, refer to Notification settings.
The following features are supported:
- Release notifications: DP can send release notifications via webhooks.
- Retrieving the changelog: Each DP release includes a changelog, available both in the cluster and as part of the release notification.
- Checking dependencies before update: Checks for component dependencies before proceeding with an update to prevent conflicts.
For more details on updating DP in air-gapped environment, see the “Updating DP in air-gapped environment” guide.