Rename field podSecurityContext to securityContext in Fluent Operator Deployment #790
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: karan k <karan.k@oracle.com>
karan56625
force-pushed
the
karak/fix_unknownfield_podSecurityContext
branch
from
97da0cf
to
34cd78e
Compare
wenchajun
approved these changes
Jun 10, 2023
benjaminhuo
approved these changes
Jun 10, 2023
karan56625
pushed a commit
to verrazzano/fluent-operator
that referenced
this pull request
Jun 12, 2023
…podSecurityContext Rename field podSecurityContext to securityContext in Fluent Operator Deployment
karan56625
pushed a commit
to verrazzano/fluent-operator
that referenced
this pull request
Jun 12, 2023
…podSecurityContext Rename field podSecurityContext to securityContext in Fluent Operator Deployment
karan56625
added a commit
to verrazzano/fluent-operator
that referenced
this pull request
Jun 12, 2023
* Merge pull request fluent#790 from verrazzano/karak/fix_unknownfield_podSecurityContext Rename field podSecurityContext to securityContext in Fluent Operator Deployment * add podSecurityContext in values.yaml for operator --------- Co-authored-by: Benjamin Huo <benjamin@kubesphere.io>
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:
Rename field podSecurityContext to securityContext in Fluent Operator Deployment. As
podSecurityContextis invalid field. The correct field is securityContextWhich issue(s) this PR fixes:
Fixes #789
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: