The first step of [1], kubeadm is necessary to be upgraded because we
need to run kubeadm upgrade plan. Then, the line shows `upgrade kubeadm:`.
However, the commandline contains kubelet also. That seens copy&paste
mistake and unnecessary. This removes it.
In addition, the format of another tab is broken. This fixes it also by
naming another tab.
[1]: https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade-1-12/#upgrade-the-control-plane
We receive a lot of customer queries around HPA not communicating with metrics-server where the core issue is that metrics-server is not installed. Feedback has been that this wasn't explicitly clear, suggesting this change in wording to assist.
* Code style not working on kubernetes.io
Code style based on tab works on github markdown, but it is not working on kubernetes.io. In addition to that, `<your-pv-name>` argument on line 50 is hidden on kubernetes.io, because it is being processed as a HTML tag.
* Update change-pv-reclaim-policy.md
Indentation fix
Language of the code specified
* fix spelling errors in content/en/docs/concepts/containers/
Signed-off-by: William Zhang <warmchang@outlook.com>
* fix spelling errors in HPA, StatefulSet, SA
Signed-off-by: William Zhang <warmchang@outlook.com>
* Updated the numbering of instructions
All of the instructions were numbered like this:
1. do something
1. then do this
1. finally, do this.
I just changed them accordingly to be 1-2-3. There was also a case typo in the `LOG_LEVEL=info` which should be `LOG_LEVEL=INFO` based on the data in the yaml file.
* Update numbered list formatting
* [WIP] test snippet fix
* more numbered list/snippet fixes
Missing the `data` label in configmap spec. Attempting to create the file as is results in:
```
error: error validating "STDIN": error validating data: ValidationError(ConfigMap): unknown field "Corefile" in io.k8s.api.core.v1.ConfigMap; if you choose to ignore these errors, turn validation off with --validate=false
```
The `/` steps expression is used throughout this doc but is never explained. Worse, it isn't actually part of the "normal" Cron spec linked in Wikipedia and is an extension added to vixiecron
* add Digital Rebar KRIB to installer lists
* second review, minor cleanups
* address corrections flagged by @neolit123
* resolve merge - fix table
* add Digital Rebar KRIB to installer lists
* second review, minor cleanups
* address corrections flagged by @neolit123
We have a redirect, so these links aren't broken, but we shouldn't
rely on the redirect - that ends up with long chains of complicated
redirects and makes validating the markdown harder.
Karen Bradshaw