Skip to content

Commit a8d1e8c

Browse files
authored
Merge pull request #37864 from Sea-n/tasks-configmap-secret
Tweak tasks/configmap-secret
2 parents 74e1f8f + 37864ab commit a8d1e8c

File tree

3 files changed

+10
-13
lines changed

3 files changed

+10
-13
lines changed

content/en/docs/tasks/configmap-secret/managing-secret-using-config-file.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -238,4 +238,3 @@ kubectl delete secret mysecret
238238
- Read more about the [Secret concept](/docs/concepts/configuration/secret/)
239239
- Learn how to [manage Secrets using kubectl](/docs/tasks/configmap-secret/managing-secret-using-kubectl/)
240240
- Learn how to [manage Secrets using kustomize](/docs/tasks/configmap-secret/managing-secret-using-kustomize/)
241-

content/en/docs/tasks/configmap-secret/managing-secret-using-kubectl.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -87,8 +87,8 @@ kubectl get secrets
8787
The output is similar to:
8888

8989
```
90-
NAME TYPE DATA AGE
91-
db-user-pass Opaque 2 51s
90+
NAME TYPE DATA AGE
91+
db-user-pass Opaque 2 51s
9292
```
9393

9494
View the details of the Secret:
@@ -143,11 +143,13 @@ accidentally, or from being stored in a terminal log.
143143
S!B\*d$zDsb=
144144
```
145145

146-
{{<caution>}}This is an example for documentation purposes. In practice,
146+
{{< caution >}}
147+
This is an example for documentation purposes. In practice,
147148
this method could cause the command with the encoded data to be stored in
148149
your shell history. Anyone with access to your computer could find the
149150
command and decode the secret. A better approach is to combine the view and
150-
decode commands.{{</caution>}}
151+
decode commands.
152+
{{< /caution >}}
151153

152154
```shell
153155
kubectl get secret db-user-pass -o jsonpath='{.data.password}' | base64 --decode
@@ -193,10 +195,8 @@ To delete a Secret, run the following command:
193195
kubectl delete secret db-user-pass
194196
```
195197

196-
<!-- discussion -->
197-
198198
## {{% heading "whatsnext" %}}
199199

200200
- Read more about the [Secret concept](/docs/concepts/configuration/secret/)
201-
- Learn how to [manage Secrets using config files](/docs/tasks/configmap-secret/managing-secret-using-config-file/)
201+
- Learn how to [manage Secrets using config file](/docs/tasks/configmap-secret/managing-secret-using-config-file/)
202202
- Learn how to [manage Secrets using kustomize](/docs/tasks/configmap-secret/managing-secret-using-kustomize/)

content/en/docs/tasks/configmap-secret/managing-secret-using-kustomize.md

Lines changed: 3 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -90,8 +90,7 @@ the Secret data and appending the hash value to the name. This ensures that
9090
a new Secret is generated each time the data is modified.
9191
9292
To verify that the Secret was created and to decode the Secret data, refer to
93-
[Managing Secrets using
94-
kubectl](/docs/tasks/configmap-secret/managing-secret-using-kubectl/#verify-the-secret).
93+
[Managing Secrets using kubectl](/docs/tasks/configmap-secret/managing-secret-using-kubectl/#verify-the-secret).
9594
9695
## Edit a Secret {#edit-secret}
9796
@@ -117,12 +116,11 @@ your Pods.
117116
To delete a Secret, use `kubectl`:
118117
119118
```shell
120-
kubectl delete secret <secret-name>
119+
kubectl delete secret db-user-pass
121120
```
122121

123-
<!-- Optional section; add links to information related to this topic. -->
124122
## {{% heading "whatsnext" %}}
125123

126124
- Read more about the [Secret concept](/docs/concepts/configuration/secret/)
127-
- Learn how to [manage Secrets with the `kubectl` command](/docs/tasks/configmap-secret/managing-secret-using-kubectl/)
125+
- Learn how to [manage Secrets using kubectl](/docs/tasks/configmap-secret/managing-secret-using-kubectl/)
128126
- Learn how to [manage Secrets using config file](/docs/tasks/configmap-secret/managing-secret-using-config-file/)

0 commit comments

Comments
 (0)