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.

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

Decide what new secrets should look like #1337

Open
duallain opened this issue Jul 13, 2020 · 0 comments
Open

Decide what new secrets should look like #1337

duallain opened this issue Jul 13, 2020 · 0 comments

Comments

@duallain
Copy link
Contributor

Examine options, making sure all of our use cases for reading secrets are handled:

  • k8s pods
  • gitlab jobs (possibly via runner)

Document/POC writing secrets as well.

Ensure we can split permissions (for futureproofing) (k8s pods can't all get to same secrets/use at least namespace for splitting?).
outcome of this story ought to be an ADR

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

No branches or pull requests

1 participant