Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Decouple API token and cloud provider token from secrets #122

Closed
viveklak opened this issue Mar 19, 2021 · 0 comments · Fixed by #125
Closed

Decouple API token and cloud provider token from secrets #122

viveklak opened this issue Mar 19, 2021 · 0 comments · Fixed by #125
Assignees
@viveklak
Labels
emergent An issue that was added to the current milestone after planning kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Milestone
0.54

Comments

@viveklak
Copy link
Contributor

Currently the stack CRD makes a strong assumption that the API token and cloud provider tokens are supplied through secrets which limits flexibility. If the operator could read these secrets from the filesystem it would allow it to work with a variety of secret management systems, e.g: (k8s secret mapped to volume, injected from Vault, AWS Secret Manager, Google Secret Manager).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@viveklak viveklak

Labels
emergent An issue that was added to the current milestone after planning kind/enhancement Improvements or new features resolution/fixed This issue was fixed
Projects
None yet
Milestone
0.54
Development

Successfully merging a pull request may close this issue.

Make environment variable population more generic pulumi/pulumi-kubernetes-operator
3 participants
@leezen @viveklak @pulumi-bot