Add admonition type to shortcode (#9482)
* Change existing admon blocks * Fix includes issue
This commit is contained in:
committed by
k8s-ci-robot
parent
e839031292
commit
d65e1790ff
@@ -140,7 +140,7 @@ previous revision through other commands, such as `kubectl edit` or `kubectl
|
||||
apply`.
|
||||
|
||||
{{< note >}}
|
||||
**Note:** DaemonSet revisions only roll forward. That is to say, after a
|
||||
DaemonSet revisions only roll forward. That is to say, after a
|
||||
rollback completes, the revision number (`.revision` field) of the
|
||||
`ControllerRevision` being rolled back to will advance. For example, if you
|
||||
have revision 1 and 2 in the system, and roll back from revision 2 to revision
|
||||
|
||||
@@ -159,9 +159,10 @@ kubectl get pods -l <daemonset-selector-key>=<daemonset-selector-value> -o wide
|
||||
```
|
||||
|
||||
Once you've found those nodes, delete some non-DaemonSet pods from the node to
|
||||
make room for new DaemonSet pods.
|
||||
make room for new DaemonSet pods.
|
||||
|
||||
{{< note >}}
|
||||
**Note:** This will cause service disruption when deleted pods are not controlled by any controllers or pods are not
|
||||
This will cause service disruption when deleted pods are not controlled by any controllers or pods are not
|
||||
replicated. This does not respect [PodDisruptionBudget](/docs/tasks/configure-pod-container/configure-pod-disruption-budget/)
|
||||
either.
|
||||
{{< /note >}}
|
||||
|
||||
Reference in New Issue
Block a user