Source: thenewstack.io
Managing Kubernetes Secrets with AWS Secrets ManagerCategory: Kubernetes
In this installment, we will leverage it to configure secrets backed by Amazon Web Services‘ Secrets Manager.
To bridge the gap between the two, they built a Kubernetes custom controller and a custom resource definition called External Secrets, which can manage and rotate the keys originating in AWS Secrets Manager for any Kubernetes deployment.
After that, we create a secret in the AWS Secrets Store and pointing it to the Kubernetes External Secret created in the local cluster.
Before we deploy the Kubernetes External Secrets custom controller, we need to register the AWS AccessKey and SecretAccessKey as Kubernetes secrets in the same namespace where the custom controller runs.
With the Kubernetes cluster connected to the AWS Secrets Manager through the External Secrets controller, we are ready to create secrets in the cloud and propagate them to the local cluster.
To bridge the gap between the two, they built a Kubernetes custom controller and a custom resource definition called External Secrets, which can manage and rotate the keys originating in AWS Secrets Manager for any Kubernetes deployment.
After that, we create a secret in the AWS Secrets Store and pointing it to the Kubernetes External Secret created in the local cluster.
Before we deploy the Kubernetes External Secrets custom controller, we need to register the AWS AccessKey and SecretAccessKey as Kubernetes secrets in the same namespace where the custom controller runs.
With the Kubernetes cluster connected to the AWS Secrets Manager through the External Secrets controller, we are ready to create secrets in the cloud and propagate them to the local cluster.
Related Articles
Community Partners
DevOps Careers