We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent a3dc78a commit ced82c8Copy full SHA for ced82c8
content/en/docs/tasks/configmap-secret/managing-secret-using-config-file.md
@@ -75,6 +75,8 @@ The following example stores two strings in a Secret using the `data` field.
75
To verify that the Secret was created and to decode the Secret data, refer to
76
[Managing Secrets using kubectl](/docs/tasks/configmap-secret/managing-secret-using-kubectl/#verify-the-secret).
77
78
+### Specify unencoded data when creating a Secret
79
+
80
For certain scenarios, you may wish to use the `stringData` field instead. This
81
field allows you to put a non-base64 encoded string directly into the Secret,
82
and the string will be encoded for you when the Secret is created or updated.
0 commit comments