AzBlob (and future OutputLocation) Config should be passed through ConfigMaps and Secrets

[rbtr]

Is your feature request related to a problem? Please describe. Currently the AzBlob OutputLocation is provided via a URL with an embedded SAS token. This URL is used as the Volume name in the Capture Pods that are created, which conveniently distributes the access credentials. This is technically a credential leak - the SAS token is readable to anyone with Pod:read instead of Secret:read.

Describe the solution you'd like The AzBlob config and secrets should be provided via Kubernetes objects for the same (ConfigMaps and Secrets).

Additional context The rework done here should be portable to other (future) OutputLocation implementations such as S3 (#201)

[iamvighnesh]

@rbtr Keen on being a contributor on this project and would like to pick this issue as my first one on the project.

[rbtr]

@iamvighnesh great, assigned it to you 🙂

[timraymond]

Hey @iamvighnesh, any updates on this one?