Conversation
The policy already rules out skipping releases and sets the operators-first order, so the guide cites it up front instead of restating either as its own advice. It also narrows the case for changing a product version before the operator upgrade to versions already deprecated, which is what the deprecation guarantee leaves.
✅ Deploy Preview for stackable-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
guides/upgrading-sdp.adoc, a release-independent guide to upgrading the Stackable Data Platform (SDP), and lists it first in the guides navigation.Until now the order of an upgrade was only implied across the per-release "Upgrade from" sections, the cluster operations page and the policies. The guide puts it in one place:
Commands that differ per release stay in the release notes and are referenced, not repeated.
The build currently fails on three unrelated warnings from the airflow-operator docs (
usage-guide/applying-custom-resources.adoc, "no callout found"), which the playbook treats as fatal. This page adds none.