-
Notifications
You must be signed in to change notification settings - Fork 62
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.
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
base: main
Are you sure you want to change the base?
mount-s3-namespace to be conditional #580
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall, left a small comment regarding the name of the variable
|
||
mountpointPod: | ||
namespace: mount-s3 | ||
namespaceEnabled: true |
There was a problem hiding this comment.
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
Issue #, if available:
#579
Description of changes:
Currently, this yaml file gets deployed without condition. We want it to have a condition that by default it can deploy or create the namespace, but if we choose to opt out of it, then don't deploy.
As we use ArgoCD to deploy it, the argo application autocreates the namespace along with certain annotations that we pass from ArgoCD. But this yaml file overrides these annotations causing the s3-csi-controller deployment to have issues
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.