- Change the describe command
- Add step numbers to decode section
- Change first step to remove excess words
- Modify password base64 string to match previous step
- Move code sample comments into a caution block
- Add brief intro to the page
- Improve the intro to the create secret section
- Split the steps for creating into subheadings for raw and file
- Keep commands the same but change the password string to be uniform
- Keep explanation of -n flag same but add line at end of note for escaping
- Keep explanation of default key name same (line 64-65)
The current example showing how to decode a secret
does it in several steps which is fine but if some level
of security is required will leak the encoded secret
value in the shell history thus making it retrievable.
This patch adds an example on how to retrieve that
value without exposing it.
There are many contents in the (*very big*) Secret concept page which
are actually tasks. This PR proposes a separation of some contents
into separate tasks, so that we have a (hopefully) better organization
of the content and we make room for improvement to the concept itself.
Note that the creation of the `configmap-secret` directory (instead of
`secret`) is an intent to create a folder for both ConfigMap and Secret,
both of which are about configurations though there are quite some
differences between them.
Shannon Kularathna
Samuel Gaist
Wiktor Kwapisiewicz
Shannon Kularathna
Kubernetes Prow Robot
Shubham Kuchhal
Karen Bradshaw
Hrishikesh Barua
Hao Yuan
Qiming Teng