Added capabilities to container security context #109
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
VenkataChalla554
force-pushed
the
1890-security-aks-container-hardening-capabilities
branch
from
88aca13 to
fd045af
Compare
VenkataChalla554
force-pushed
the
1890-security-aks-container-hardening-capabilities
branch
from
fd045af to
9869533
Compare
VenkataChalla554
changed the title
saliceti
approved these changes
Jul 4, 2024
VenkataChalla554
deleted the
1890-security-aks-container-hardening-capabilities
branch
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.
Context
Added security context for container
Changes proposed in this pull request
Added security context capabilities for container
Guidance to review
Deployed review app on cluster2 it is working with out any issues (https://github.com/DFE-Digital/register-trainee-teachers/tree/1890-security-aks-container-hardening-capabilities-test)
After merging
After deployment , this changes can be verified as below.
` kubectl -n development get po register-2222-5994967dbd-x7mxh -o jsonpath='{.spec.containers[*].securityContext}'
{"allowPrivilegeEscalation":false,"capabilities":{"add":["NET_BIND_SERVICE"],"drop":["ALL"]},"privileged":false,"readOnlyRootFilesystem":false,"runAsNonRoot":false,"seccompProfile":{"type":"RuntimeDefault"}}
`
Checklist
Devopslabel