Added docs for kubernetes.io/description
parent
2d6d22ddec
commit
4b91d983d6
|
@ -72,6 +72,14 @@ This annotation is a best guess at why something was changed.
|
|||
|
||||
It is populated when adding `--record` to a `kubectl` command that may change an object.
|
||||
|
||||
## kubernetes.io/description {#description}
|
||||
|
||||
Example: `kubernetes.io/description: "Description of K8s object."`
|
||||
|
||||
Used on: All Objects
|
||||
|
||||
This annotation is used for describing specific behaviour of given object.
|
||||
|
||||
## controller.kubernetes.io/pod-deletion-cost {#pod-deletion-cost}
|
||||
|
||||
Example: `controller.kubernetes.io/pod-deletion-cost=10`
|
||||
|
@ -464,4 +472,4 @@ This annotation has been deprecated since Kubernetes v1.19 and will become non-f
|
|||
The tutorial [Restrict a Container's Syscalls with seccomp](/docs/tutorials/clusters/seccomp/) takes
|
||||
you through the steps you follow to apply a seccomp profile to a Pod or to one of
|
||||
its containers. That tutorial covers the supported mechanism for configuring seccomp in Kubernetes,
|
||||
based on setting `securityContext` within the Pod's `.spec`.
|
||||
based on setting `securityContext` within the Pod's `.spec`.
|
||||
|
|
Loading…
Reference in New Issue