fix: fluentd watchedNamespaces Helm mapping #901
Merged
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: leonsteinhaeuser <[email protected]>
|
Relates to: fluent/helm-charts#412 |
benjaminhuo
approved these changes
Sep 2, 2023
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.
What this PR does / why we need it:
To be able to set an empty array for watchedNamespaces, we need to change the way properties are added. Currently, if we set an empty array as a property, we get the following error message:
ClusterFluentdConfig.fluentd.fluent.io "fluentd-config" is invalid: spec.watchedNamespaces: Invalid value: "null": spec.watchedNamespaces in body must be of type array: "null". The reason for this error message is that[]does not count as a value with an index, so the CR key is set tonull, which is not a valid value.Which issue(s) this PR fixes:
See description above.
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: