Update pod security context schema in cert-manager #538
Conversation
This file contains hidden or 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
max-lobur
changed the title
This feature was deprecated in newer k8s and does not pass Deployment validation.
max-lobur
force-pushed
the
max-lobur-patch-2
branch
from
72d3e1a to
0002125
Compare
milldr
approved these changes
Jan 19, 2023
goruha
pushed a commit
to cloudposse-terraform-components/aws-eks-cert-manager
that referenced
this pull request
Nov 27, 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
Pod security context
enabledfield has been deprecated. Now you just specify the options and that's it.Update the options per recent schema. See references
Tested on k8s 1.24
why
references
cert-manager/cert-manager@c17b11f