You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem description
We currently do not have a robust solution for storing & managing the SOPS GPG keys that are used for encryption & decryption within Airship. Current downstream implementations involve generating & storing secrets through Jenkins pipelines and are less than ideal.
Proposed change
Define an integration solution to provide GPG key management. It should be a system that provides certain capabilities like secure key storage, role based access control (RBAC), key distribution, mutating admission control and/or controller that injects keys as needed.
Problem description
We currently do not have a robust solution for storing & managing the SOPS GPG keys that are used for encryption & decryption within Airship. Current downstream implementations involve generating & storing secrets through Jenkins pipelines and are less than ideal.
Proposed change
Define an integration solution to provide GPG key management. It should be a system that provides certain capabilities like secure key storage, role based access control (RBAC), key distribution, mutating admission control and/or controller that injects keys as needed.
One of the main options include Vault:
https://www.vaultproject.io/docs/platform/k8s
https://github.com/hashicorp/vault-k8s
While this issue may also be used to implement, the main purpose is to provide the design & approach for GPG key management.
Potential impacts
Need to ensure that encryption keys are securely stored and only accessible by authorized personnel.
The text was updated successfully, but these errors were encountered: