Working with secrets
Kubernetes secrets manage information in key-value formats with the value encoded. With secrets, users don't have to set values in the configuration file or type them in CLI. When secrets are used properly, they can reduce the risk of credential leak and make our resource configurations more organized.
Currently, there are three types of secret:
- Opaque: https://en.wikipedia.org/wiki/Opaque_data_type
- Service account token
- Docker authentication
Opaque is the default type. We will put service account tokens and the authentication of Docker in the remark part.
Getting ready
Before using our credentials with secrets, some precautions must be taken First, secrets have a 1 MB size limitation. It works fine for defining several key-value ...
Get DevOps: Puppet, Docker, and Kubernetes now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
