Secrets management from a CI/CD perspective
Managing Secrets in CI/CD pipelines is an interesting concept. In previous chapters, we focused primarily on the Git-based concept of Secrets management and the secret-storage-based Secrets management. We have not mentioned manual secret persistence to Kubernetes. There are many reasons for that:
- You lose track of your Kubernetes deployment needs
- Dependencies are not visible
- No clear depiction of what is applied
- Not compatible with infrastructure as code
Next, we will focus on interacting with Secrets on our CI/CD pipelines.
Integrating Secrets management into your CI/CD process
Your CI/CD strategy will differ significantly depending on the approach taken for managing Secrets.
Git-based Secrets management
By managing Secrets through a Git-based approach, CI/CD should be able to interact with the components involved.
Depending on the encryption mechanism, you need to have credentials configured on...