Merge pull request #9728 from ashley-cui/secretdocs

[CI:DOCS] removing secrets is safe for in-use secrets
This commit is contained in:
OpenShift Merge Robot 2021-03-17 02:27:54 -07:00 • committed by GitHub
commit 9439b699b8
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
3 changed files with 16 additions and 0 deletions

View file

@ -833,6 +833,11 @@ A secret is a blob of sensitive data which a container needs at runtime but
should not be stored in the image or in source control, such as usernames and passwords,
TLS certificates and keys, SSH keys or other important generic strings or binary content (up to 500 kb in size).
Secrets are copied and mounted into the container when a container is created. If a secret is deleted using
`podman secret rm`, the container will still have access to the secret. If a secret is deleted and
another secret is created with the same name, the secret inside the container will not change; the old
secret value will still remain.
Secrets are managed using the `podman secret` command.
#### **--security-opt**=*option*

View file

@ -885,6 +885,11 @@ A secret is a blob of sensitive data which a container needs at runtime but
should not be stored in the image or in source control, such as usernames and passwords,
TLS certificates and keys, SSH keys or other important generic strings or binary content (up to 500 kb in size).
Secrets are copied and mounted into the container when a container is created. If a secret is deleted using
`podman secret rm`, the container will still have access to the secret. If a secret is deleted and
another secret is created with the same name, the secret inside the container will not change; the old
secret value will still remain.
Secrets are managed using the `podman secret` command
#### **--security-opt**=*option*

View file

@ -10,6 +10,12 @@ podman\-secret\-rm - Remove one or more secrets
Removes one or more secrets.
`podman secret rm` is safe to use on secrets that are in use by a container.
The created container will still have access to the secret data because secrets are
copied and mounted into the container when a container is created. If a secret is deleted and
another secret is created with the same name, the secret inside the container will not change;
the old secret value will still remain.
## OPTIONS
#### **--all**, **-a**