Fix values.schema.json - containerSecurityContext is an instance of io.k8s.api.core.v1.SecurityContext #337
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
milesarmstrong
changed the title
milesarmstrong
force-pushed
the
miles/update-json-schema
branch
from
d31e3c3 to
8b494b3
Compare
…SecurityContext, otherwise some fields are invalid
milesarmstrong
force-pushed
the
miles/update-json-schema
branch
from
8b494b3 to
968f1ae
Compare
|
LGTM @jamengual |
jamengual
approved these changes
Nov 16, 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
Update the JSON schema to reflect that
containerSecurityContextinvalues.yamlcan be an instance ofio.k8s.api.core.v1.SecurityContextwhy
To allow the full range of Security Context settings, for instance, we use
capabilities.tests
Checked with https://www.jsonschemavalidator.net/
references
N/A