Add Interface to Helm Chart for Secrets Store CSI Driver Integration

[augustkang]

Hi!

I'm currently using the falcon-sensor Helm chart for deployments, and I've noticed some security and operational concerns regarding how credentials, like image pull secrets and Falcon API tokens, are managed within the existing chart.

Specifically, the current setup lacks a clear interface in values.yaml to securely integrate external secret management solutions, such as the Secrets Store CSI Driver. Introducing this functionality would also involve adding a dedicated template (secretproviderclass) to the chart's templates directory.

Would you be open to providing a well-defined interface within values.yaml to enable users to securely inject credentials using Secrets Store CSI Driver?

I'd appreciate hearing your thoughts on this.

[VillageIke]

10000% this

[gpontejos]

Hi! I'd be down to implement this. I don't really see any issues with just adding a secretproviderclass and having users fill in the parameters while we define the secret objects. We currently have falconSecret available in most of our charts if you wanted to utilize the External Secrets Operator in the meantime. I have a ticket on our side for this. I'll keep you updated.

[ross-c-swyftx]

Any updates?

[john-r-swyftx]

@gpontejos Any updates on this? We would prefer to use secretproviderclass instead of having another controller to manage our secrets 🙏

[TomRyan-321]

@gpontejos I've raised #515 to cover this