docs: move atomic manifest updates to other page#2302
Open
davidweisse wants to merge 1 commit intomainfrom
Open
docs: move atomic manifest updates to other page#2302davidweisse wants to merge 1 commit intomainfrom
davidweisse wants to merge 1 commit intomainfrom
Conversation
Do the documentation changes need to be backported?Changes to
|
|
burgerdev
approved these changes
Apr 8, 2026
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
2 participants
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.
We have two pages that explain the process of setting a manifest. Since the
workload-deployment/set-manifestpage is more or less part of a step-by-step guide in getting a deployment running, I feel like detailed explanations and alternatives fit better under themanifest-updatepage. This will then also be the place for documenting signed manifest updates.