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

Encryption provider key rotation #791

Closed
alex-dabija opened this issue Feb 7, 2022 · 1 comment
Closed

Encryption provider key rotation #791

alex-dabija opened this issue Feb 7, 2022 · 1 comment
Assignees
Labels
area/kaas Mission: Cloud Native Platform - Self-driving Kubernetes as a Service kind/story provider/azure Related to cloud provider Microsoft Azure target-release/17.1.0 team/phoenix Team Phoenix topic/security

Comments

@alex-dabija
Copy link

alex-dabija commented Feb 7, 2022

User Story

- As a cluster admin, I want the Kubernets API encryption provider key to be rotated in order follow security best practices.

Details, Background

Requirements

  • Encryption provider key rotation should work the same way for all providers, including Cluster API clusters;
  • Key rotation frequency should be externally configurable;

Blocked by / depends on

None

@alex-dabija alex-dabija added area/kaas Mission: Cloud Native Platform - Self-driving Kubernetes as a Service team/phoenix Team Phoenix kind/task labels Feb 28, 2022
@alex-dabija alex-dabija changed the title azure - use encryption-provider-operator for encryption keys and rotation Encryption provider key rotation Feb 28, 2022
@whites11 whites11 self-assigned this Jun 14, 2022
@whites11
Copy link

released in azure operator 15.21.0, will be part of release 17.1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kaas Mission: Cloud Native Platform - Self-driving Kubernetes as a Service kind/story provider/azure Related to cloud provider Microsoft Azure target-release/17.1.0 team/phoenix Team Phoenix topic/security
Projects
None yet
Development

No branches or pull requests

2 participants