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

[Spike][Security] I want to remove k8s secrets in order to improve security in production #17

Open
3 tasks
6l20 opened this issue Nov 10, 2021 · 0 comments

Comments

@6l20
Copy link
Contributor

6l20 commented Nov 10, 2021

Summary / User Story

It is not recommended to use k8s secrets in a prod environment, a better solution would consist in havin secrets managed by a dedicated Vault or managed solution depending on the target cloud platform.

Pre-requisites

  • Having stable deployments ready
  • Having "sandbox" clusters available
  • Having identified, categorized and qualified all sensitive data
  • For each targeted cloud PF identify all possible solutions
  • For each targeted cloud PF identify the best Vault solution

Technical Notes

  • Links to architecture, documents

Business Value

Minimize Threats from insiders / increase overall security level

Acceptance Criteria

  • Have at least one POC running for each possible cloud PF. (add list below on the go)
  • Write technical / architecture documentation related to each and every solution
  • Have helm and k8s charts updated accordingly
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