Fix incorrect placeholder value for kafkaSecrets, adding few more examples for volumes related values #1712
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
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.
Default value of kafkaSecret does not reflect how the value is handled in secret.yaml#L15 template - it should be an object not an array. Another possible solution would be to change the template but I find it to be more invasive while my change is mostly documentation.
Example:
Parsed incorrectly:
Parsed correctly:
I have also included few more examples of how to define the aforementioned keystore/truststore and how to mount them.
Thank you for the work on AKHQ project, it's amazing!