fix init db to actually provision with a secret #286
Closed
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
Signed-off-by: 8ball030 <[email protected]>
|
I believe theere additional issues in in that when you try to use this configuration option, the new database is not correctly configured to use the secret specified. Any guidance on this would be appreciated and i can update the pr to provide more clarity to others. |
|
Can you share the values you are experiencing an issue with? |
|
Closing in favor of: #239 |
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.
helm.go:84: [debug] admission webhook "mcluster.cnpg.io" denied the request: json: cannot unmarshal string into Go struct field BootstrapInitDB.spec.bootstrap.initdb.secret of type v1.LocalObjectReference
The defazult values fail to provision,
In order to get the secret to work, you have to add the name key,.