Skip to content

Conversation

harshashenoy98
Copy link

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.

@harshashenoy98 harshashenoy98 requested a review from a team as a code owner September 11, 2025 12:22
Copy link
Contributor

@muddyfish muddyfish left a 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
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

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