Kubernetes Cluster Configuration Concepts: Difference between revisions
| Line 15: | Line 15: | ||
Secrets can also be used by other parts of the system, without being directly exposed to pods. | Secrets can also be used by other parts of the system, without being directly exposed to pods. | ||
==Secret Types== | |||
===Opaque=== | |||
===kubernetes.io/service-account-token=== | |||
==Secrets Operations== | ==Secrets Operations== | ||
* [[Kubernetes_Secrets_Operations#With_kubectl_CLI|Create a Secret with kubectl CLI]] | * [[Kubernetes_Secrets_Operations#With_kubectl_CLI|Create a Secret with kubectl CLI]] | ||
* [[Kubernetes_Secrets_Operations#From_a_Manifest|Create a Secret from a manifest]] | * [[Kubernetes_Secrets_Operations#From_a_Manifest|Create a Secret from a manifest]] | ||
Revision as of 17:16, 22 August 2019
Internal
Secrets
A secret is a mechanism, backed by a Kubernetes API resource, that allows applications running on a Kubernetes cluster to safely manage, store and access security-sensitive information such as passwords, OAuth tokens and ssh keys. This mechanism provides a better alternative to placing that information in a container image or in the pod metadata. An individual secret contains a small amount of data, limited to 1 MiB - this is to discourage creation of very large secrets that would exhaust API server and kubelet memory.
Secrets are consumed by applications, and they can be exposed to pods in two ways:
- As files in dedicated volumes mounted in the pod.
- As environment variables exposed to containers in the pod.
A pod must explicitly reference a secret in its manifest to access it. If that does not happen, the system will not initialize the infrastructure that exposes the information to the pod.
Secrets can also be used by other parts of the system, without being directly exposed to pods.