kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

improve explanation on when to use 'data' and 'stringData' fields

This commit is contained in:
Mike Mwanje 2023-06-29 15:05:31 +00:00
parent 2649069270
commit b6ae431591
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
content/en/docs/concepts/configuration/secret.md
View File

@ -846,7 +846,7 @@ When using this type of Secret, the `tls.key` and the `tls.crt` key must be prov
in the `data` (or `stringData`) field of the Secret configuration, although the API
server doesn't actually validate the values for each key.
Use the `stringData` field to add the certificate and private key directly to the secret. Use the `data` field to provide base64 encoded values of both the certificate and private key. Refer to [Constraints on Secret names and data](#restriction-names-data) for more on this.
As an alternative to using `stringData`, you can use the `data` field to provide the base64 encoded certificate and private key. Refer to [Constraints on Secret names and data](#restriction-names-data) for more on this.
The following YAML contains an example config for a TLS Secret: