Loading
Resolve "Feature Request: Allow mounting Agent Access Token through CSI Secret Store"
This MR:
- Adds support for providing the agent access token through a CSI Secret Store SecretProviderClass (see issue #80 (closed) on why this is useful).
- Fixes the code of conduct link (which was broken) in Contributing.md
Implementation notes
- I decided to make the old token / native Kubernetes flow mutually exclusive with the new CSI Secret Store support. Main rationale: In this way we can re-use the mount path that was already defined for the secret volume, as the behaviour of the CSI Secret Store providers is very similar to mounting a native Kubernetes Secret as a volume. However, using both simultaneously would result in two volumes on the deployment with exactly the same name, and therefore would cause clashes.
Closes #80 (closed)