Skip to content

Conversation

@BrendanGalloway
Copy link
Contributor

No description provided.

@BrendanGalloway BrendanGalloway requested a review from moshloop May 19, 2023 09:48
@netlify
Copy link

netlify bot commented May 19, 2023

Deploy Preview for elaborate-horse-ac1743 ready!

Name Link
🔨 Latest commit 6809694
🔍 Latest deploy log https://app.netlify.com/sites/elaborate-horse-ac1743/deploys/646c831b5f97e30008c6e93a
😎 Deploy Preview https://deploy-preview-1007--elaborate-horse-ac1743.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

Comment on lines +64 to +76
{{- define "canary-checker.containerSecurityContext" -}}
allowPrivilegeEscalation: {{- if eq ( lower .Values.privilegeMode ) "privileged" }}true{{- else }}false{{- end }}
{{- if has ( lower .Values.privilegeMode) ( list "privileged" "root" ) }}
runAsUser: 0
runAsGroup: 0
fsGroup: 0
{{- if eq ( lower .Values.privilegeMode ) "privileged" }}
capabilities:
add:
- CAP_NET_RAW
{{- end }}
{{- end }}
{{- end }}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The fsGroup setting belongs in the pod's securityContext block, not the container's. This is because file system group IDs are a pod-level configuration that applies to all containers. Consider moving this setting to a separate helper template that's included in the pod's securityContext section of the deployment manifest.

Spotted by Graphite Reviewer

Is this helpful? React 👍 or 👎 to let us know.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants