docs: README.md - fix secret name #70
Open
Conversation
This file contains 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
Copy and pasting the current docs does not lead to a successful installation of the helm chart if you use the <STACKIT AUTH TOKEN>. You have to change the helm value to meet the kubectl command `stackitSaAuthentication.secretName = "stackit-cert-manager-webhook"`. As an alternative i would propose a consistent naming for both secret types as it is treaded equal in the helm chart.
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.
Copy and pasting the current docs does not lead to a successful installation of the helm chart if you use the
<STACKIT AUTH TOKEN>.You have to change the helm value to meet the kubectl command
stackitSaAuthentication.secretName = "stackit-cert-manager-webhook".As an alternative i would propose a consistent naming for both secret types as it is treaded equal in the helm chart.