-
Notifications
You must be signed in to change notification settings - Fork 6.5k
docs: Change reference URL for HA manifests to stable. #24049
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Change reference URL for HA manifests to stable. #24049
Conversation
❌ Preview Environment deleted from BunnyshellAvailable commands (reply to this comment):
|
Signed-off-by: Fox Danger Piacenti <[email protected]>
8e8a4ab to
cc9a955
Compare
|
Thanks for the PR @Kelketek ! Can you create cherry-pick PRs for |
|
@reggie-k All three have failed CI. Not sure if you need me to do anything there, since I wouldn't expect a link in the docs to cause a problem. |
|
@Kelketek thanks! I merged all of them. The error is indeed unrelated to the change and is a common issue with PR against release branches. |
Signed-off-by: Fox Danger Piacenti <[email protected]> Signed-off-by: Mangaal <[email protected]>
Signed-off-by: Fox Danger Piacenti <[email protected]>
Signed-off-by: Fox Danger Piacenti <[email protected]> Signed-off-by: Hapshanko <[email protected]>
Signed-off-by: Fox Danger Piacenti <[email protected]>
Description
This Merge request updates the URL in the High-Availability documentation to point to the stable branch, just as the getting started documentation has. Using the master version of the installation manifests by mistake can cause hours of wasted time on behalf of the operator. Ask me how I know. :)
Recommended cherry-picks
Whatever version of the docs is currently published (stable?) should have this commit cherry-picked.
Checklist
I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.Does this PR require documentation updates?I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.My new feature complies with the feature status guidelines.Optional. My organization is added to USERS.md.