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

Extend "encrypt-at-rest" to support integration with KMS #11531

Open
andrey-podko opened this issue Sep 13, 2024 · 3 comments
Open

Extend "encrypt-at-rest" to support integration with KMS #11531

andrey-podko opened this issue Sep 13, 2024 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@andrey-podko
Copy link

What would you like to be added

Would be great to get out-of-box integration with KMSv2 plugins like

Also would be great to have there convenient support of encryption key rotation instead 1 key for all times ). Unfortunately current implementation overwrites all changes in secrets_encryption.yaml and every cluster update breaks the encrypt-at-rest.

apiServer:
  extraArgs:
    encryption-provider-config-automatic-reload: true

This also can be a good option

KMSv2 is stable since kubernetes 1.29

Why is this needed

That's needed to have possibility of using external encryption keys/services for cases like "someone stole content/backups of etcd/control-plane"

@andrey-podko andrey-podko added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 13, 2024
@tico88612
Copy link
Member

You can try kube_kubeadm_apiserver_extra_args.

@andrey-podko
Copy link
Author

Yes, and it should works, but would be very nice to have it out-of-box, like aes encryption

@tico88612
Copy link
Member

If you would like to see this become an option or variable, you (or anyone else) are welcome to open a PR to discuss it with us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants