After deploying the PV and PVC via the YAML file, run `kubectl describe pvc mysql-pv-claim` should show `mysql-pv-volume` as the `Volume`, instead of `mysql-pv`.
This heading is missing in the 1.10 documentations which makes it hard to find the needed information because the anchor `setting up a master load balancer` points to nowhere. This was working in the 1.19 documentation and it was really useful.
I noticed that the three last headers were missing from the index, so I inspected the markdown and realized that they had only one hashtag (#) as compared to two (##) as all the other headers had.
I simply made those three topics follow the same pattern I observed the other did.
# Issue
The command of jobs does not run correctly if its job already finished.
Some readers may confuse that they can't succeed to run a command to follow this tutorial.
So, we should add `--show-all` option to show pods that may be completed.
# The log to show that we need to add an --show-all option
```
$ kubectl get jobs
NAME DESIRED SUCCESSFUL AGE
busybox 1 0 27d
hello-1529501040 1 1 2m
hello-1529501100 1 1 1m
hello-1529501160 1 1 43s
$ kubectl get pods --selector=job-name=hello-1529501160
No resources found, use --show-all to see completed objects.
$ kubectl get pods --show-all --selector=job-name=hello-1529501160
NAME READY STATUS RESTARTS AGE
hello-1529501160-dckjv 0/1 Completed 0 1m
```
Those links are dead, pointing at what I assume in the previous place for the Kubelet TLS bootstrapping documentation.
Update them with the new location!
* Update etcd config description of kubeadm HA doc
- Fix url from http to https
- Add etcd-listen-ip description
* Edit for clarity and list markup
* More minor edits
* Add Dockerfile and make commands
* add background run option
* Expand on OSS attribution in new Dockerfile
* Begin adding README instructions for Docker
* Add new stage command
implementation-details.md is outdated for k8s 1.11.
Add feature state that this page applies to k8s 1.10.
The page should be updated for k8s 1.11 in a later stage
in the release cycle.
commenting out the div that holds the current calendar until we can fix some issues we are having with zoom project wide per steering committee email to k-dev mailing list.
`base64` generates 76-character chunks of text, delimited by a space character. the `=+/` characters are removed, so on the (uniformly random) offchance that 44 characters are removed, the last `dd` will read a whitespace, and the token will include a whitespace, which "usually" isn't defined as an "alphanumeric character." Removing the space character as well, would mean that 142 of the characters would have to be a `=+/[:space:]`, before the token becomes shorter.
* [docs] Fix syntax formatting in HA-setup doc.
Attempts to fix an unformatted code block; whatever markdown parser is being used seems to have gotten tripped up, and as a result the inline `yaml` in the script is interpreted as bullet points... it looks [pretty yucky](http://jstu.art/sAjc). I'm wondering if this is something specific to the Hugo toolchain? Because GH itself recognizes the block as valid, even with the `none` syntax type.
If this doesn't trigger a CI build preview, I can test locally to verify.
* [css] Don't display ul/li bullets on UI 'tabs-nav' components.
* [docs] Revert HA docs changes.
This reverts commit f5cf5c7e4f.