We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I run a cluster that has a policy engine on it that forbids insecure pods/containers.
Currently there is a way to define a pod security context, but not a container security context.
Can we add this in please? It just needs to be a new line in the container spec.
This is what I require:
podSecurityContext: runAsGroup: 2000 runAsNonRoot: true runAsUser: 1000 fsGroup: 2000 seccompProfile: type: RuntimeDefault containerSecurityContext: allowPrivilegeEscalation: false readOnlyRootFilesystem: true seccompProfile: type: RuntimeDefault capabilities: drop: ["ALL"]
The text was updated successfully, but these errors were encountered:
Easy workaround :
helm template --namespace k8s-pod-restart-info-collector --set slackWebhookUrl="https://hooks.slack.com/XXXXXXXXXXXXXXXXXXXXXXXXXXX" --set clusterName="k8s" --set slackChannel="k8s" . > k8s-pod-restart-info-collector.yaml
And you edit your deployment.
Sorry, something went wrong.
No branches or pull requests
Hi,
I run a cluster that has a policy engine on it that forbids insecure pods/containers.
Currently there is a way to define a pod security context, but not a container security context.
Can we add this in please? It just needs to be a new line in the container spec.
This is what I require:
The text was updated successfully, but these errors were encountered: