Skip to content

mount-s3-namespace to be conditional #580

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −0
Open

mount-s3-namespace to be conditional #580

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions charts/aws-mountpoint-s3-csi-driver/templates/mount-s3-namespace.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,9 @@
{{- if .Values.mountpointPod.namespaceEnabled }}
apiVersion: v1
kind: Namespace
metadata:
name: {{ .Values.mountpointPod.namespace }}
labels:
name: {{ .Values.mountpointPod.namespace }}
pod-security.kubernetes.io/enforce: restricted
{{- end }}
1 change: 1 addition & 0 deletions charts/aws-mountpoint-s3-csi-driver/values.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,7 @@ controller:

mountpointPod:
namespace: mount-s3
namespaceEnabled: true
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd change the name to createNamespace - the namespace is still required to use the driver, but the use case for this flag is assuming it's pre-configured

priorityClassName: mount-s3-critical
preemptingPriorityClassName: mount-s3-preempting-critical
headroomPriorityClassName: mount-s3-headroom
Expand Down
Loading