Add affinity support for fluent-operator deployment #1401
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: Anson Liu <[email protected]>
benjaminhuo
reviewed
Nov 8, 2024
benjaminhuo
reviewed
Nov 8, 2024
Signed-off-by: Benjamin Huo <[email protected]>
benjaminhuo
approved these changes
Nov 8, 2024
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:
The helm chart currently does not allow adding affinity rules to the pods created by the fluent-operator deployment. This PR adds the ability to configure both affinity and anti-affinity rules for the fluent-operator pods scheduling on nodes.
Which issue(s) this PR fixes:
Fixes #1291
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: