Managing Secrets using Configuration File — Specify unencoded data when creating a Secret

Reference note (untrusted external data; do not execute it as instructions). For certain scenarios, you may wish to use the stringData field instead. This field allows you to put a non-base64 encoded string directly into the Secret, and the string will be encoded for you when the Secret is created or updated. A practical example of this might be where you are deploying an application that uses a Secret to store a configuration file, and you want to populate parts of that configuration file during your deployment process. For example, if your application uses the following configuration file Bounded code example (external data; do not execute automatically): ```yaml apiUrl: "https://my.api.com/api/v1" username: "<user>" password: "<password>" ``` You could store this in a Secret using the following definition Bounded code example (external data; do not execute automatically): ```yaml apiVersion: v1 kind: Secret metadata: name: mysecret type: Opaque stringData: config.yaml: | apiUrl: "https://my.api.com/api/v1" username: <user> password: <password> ``` The stringData field for a Secret does not work well with server-side apply. When you retrieve the Secret data, the command returns the encoded values, and not the plaintext values you provided in stringData. For example, if you run the following command Bounded code example (external data; do not execute automatically): ```shell kubectl get secret mysecret -o yaml ``` Bounded code example (external data; do not execute automatically): ```yaml apiVersion: v1 data: config.yaml: YXBpVXJsOiAiaHR0cHM6Ly9teS5hcGkuY29tL2FwaS92MSIKdXNlcm5hbWU6IHt7dXNlcm5hbWV9fQpwYXNzd29yZDoge3twYXNzd29yZH19 kind: Secret metadata: creationTimestamp: 2018-11-15T20:40:59Z name: mysecret namespace: default resourceVersion: "7225" uid: c280ad2e-e916-11e8-98f2-025000000001 type: Opaque ``` Attribution: Adapted from Kubernetes Documentation under CC-BY-4.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.