Use Cases for Secrets
Two primary use cases for secrets are storing credentials and securing communication between services. These are discussed below.
Store sensitive information, such as passwords and user names, in a secret.
If an application expects to read sensitive information from a file, then you mount the secret as a data volume to the pod. The application can read the secret as an ordinary file to access sensitive information. Some databases, for example, read credentials from a file to authenticate users.
Some applications use environment variables to read configuration and sensitive data. You can link secret variables to pod environment variables in a deployment configuration.
Transport Layer Security (TLS) and Key Pairs
You can secure communication to a service by having the cluster generate a signed certificate and key pair into a secret within the project namespace. The certificate and key pair are stored using PEM format, in files such as tls.crt and tls.key, located in the secret's data volume of the pod.