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

[RFE] KMS migration helper #105

Open
romdalf opened this issue Jun 9, 2022 · 1 comment
Open

[RFE] KMS migration helper #105

romdalf opened this issue Jun 9, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@romdalf
Copy link
Contributor

romdalf commented Jun 9, 2022

-->Is it linked to a user story? (use the "#" to tag the user story)

#50 - Result of Design meeting held on June 9th 2022 with @cvlc @mhmxs @vfiftyfive @rovandep

-->What do we want to build?

Trousseau to migrate from one KMS provider to another

-->Why do we want to build it?

Chaning KMS is not a common operation but if it happens it should done in a smooth and secure way.
As Trousseau is the broker between the k8s api manager and the KMS, it should help in replacing the secrets encrypted with the old KMS with the new KMS.

-->How do we want to design it?

#103 will provide the ability to run contiguous KMS provider plugin in sidecars
This will help to perform a replace transaction in a secure and transparent way.
A safe switch might need to be thought of to handle this migration with a human validation.

@romdalf romdalf added the enhancement New feature or request label Jun 9, 2022
@romdalf romdalf added this to the KMS Pluging Redesign milestone Jun 9, 2022
@romdalf
Copy link
Contributor Author

romdalf commented Jul 25, 2022

Migration scenario is carried within v2.
Documentation has to be writtent.

@romdalf romdalf removed this from the KMS Pluging Redesign - Trousseau v2 milestone Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

4 participants