Fix SecureGuard installation docs - #2237
Open
abuango wants to merge 1 commit into
Open
Conversation
Contributor
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Add pull-secret values wiring, namespace creation, node sizing, RBAC and helm test steps, version pinning, and an uninstall section. Signed-off-by: Abubakar Siddiq Ango <abubakar@kubermatic.com>
abuango
force-pushed
the
secureguard-installation-devex
branch
from
July 29, 2026 03:07
90b3c77 to
7cbdfdf
Compare
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
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.
Fixes found while installing SecureGuard from these docs end to end.
installation/
kubectl create namespacebefore the secret command — following the page top to bottom failed on its first command.helm test secureguardas the verification step. The chart ships the test and the NOTES advertise it; it appeared on no doc page.--versionpinning on the Managed install.<release>-openbao-keys,<release>-dex-admin, and the five CRDs installed by a pre-install hook all outlivehelm uninstall.getting-started/
--create-namespacefrom the install, and renumbers the rest.troubleshooting/
Pods Stuck in ImagePullBackOffas the first General Issues entry. It is the most likely first failure and was undocumented.