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
The sealed secret operator pod starts will generate a new private key if one does not exist within the cluster. Currently, the private key that is used to decrypt all existing secrets is stored in git-crypt and manually applied post-setup of Flux in the cluster using the install/sealed-secret.sh script.
Ideally, Flux being integrated with git-crypt means Flux will have the capability to check out the private key within the cluster and apply it without requiring manual intervention after the operator has already initialized it.
Issue-Label Bot is automatically applying the label feature_request to this issue, with a confidence of 0.97. Please mark this comment with 👍 or 👎 to give our bot feedback!
xunholy
changed the title
Enable Flux to integrate with git-crypt to apply existing sealed secret private key
Enable FluxCD to integrate with git-crypt to apply existing sealed secret private key
Jul 12, 2020
Details
The sealed secret operator pod starts will generate a new private key if one does not exist within the cluster. Currently, the private key that is used to decrypt all existing secrets is stored in git-crypt and manually applied post-setup of Flux in the cluster using the
install/sealed-secret.sh
script.Ideally, Flux being integrated with git-crypt means Flux will have the capability to check out the private key within the cluster and apply it without requiring manual intervention after the operator has already initialized it.
https://github.com/bitnami-labs/sealed-secrets#managing-existing-secrets
The text was updated successfully, but these errors were encountered: