Specify init container resources for fluent-operator deployment #817
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: Gyorgy Nadaban <[email protected]>
gnadaban
force-pushed
the
bugfix/gee/add-missing-resources-for-init-containers
branch
from
0caac3c
to
df4f02e
Compare
benjaminhuo
approved these changes
Jul 3, 2023
|
@gnadaban Thanks! |
|
Hey @benjaminhuo , when is this expected to be released? |
@gnadaban Hopefully in a few days. |
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:
Not having resources specified for init containers prevents deployments in environments where resource definitions are mandated by policy.
Which issue(s) this PR fixes:
Fixes #816
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.:
None.