* Use feature-state note for CRI
* Note applicability to Linux hosts
* Explain cgroup ("control group")
* De-emphasize cgroup details
The individual runtime install steps already take account of this
advice.
* Revising bluemix.net links to cloud.ibm.com
* bluemix.net links are deprecated and no longer updated
* updated to new cloud.ibm.com link style
* Removing blog content
* setup/cri: add a section about cgroup drivers
A cgroup driver is an important setting for the CRI and the kubelet.
Add a section that explains why "systemd" is the suggested value
for a driver when installing a CRI.
In the case of Docker the kubelet will receive this value automatically.
For the other CRIs, the users should tackle this manually.
* Update cri.md
* Update building-from-source.md
Update the page to be consistent with the concepts template.
* Update building-from-source.md
Update the page to be consistent with the concepts template.
Since minikube v0.33.0 the default CNI config is not being provisioned
by default (https://github.com/kubernetes/minikube/pull/3441). Therefore,
we need to pass `--enable-default-cni` when starting minikube.
There is output of `kubeadm init` in create-cluster-kubeadm page.
But it is little old.
Some processes aren't included in it.
This update `kubeadm init` output to latest.
Since Kubernetes 1.10, the only supported CRI version is v1alpha2. However,
rktlet does not support that version and development seems stopped.
As there is no way to use rktlet with k8s >= 1.10, it's best to just remove
the rkt link from the "Install runtime" section of "Install kubeadm".
Signed-off-by: Rostislav M. Georgiev <rostislavg@vmware.com>
* kubeadm: add a caution about certs in HA document
* Update content/en/docs/setup/independent/high-availability.md
Co-Authored-By: neolit123 <neolit123@gmail.com>
If there is a combination of `systemctl` commands where in one you are
enabling it and in another you are starting it, that can be done in one
single command with an additional flag called `--now`. This commit
changes those two command steps in docs to one command.
The help of systemctl shows the following explanation of `--now`:
```
Start or stop unit in addition to enabling or disabling it
```
Signed-off-by: Suraj Deshmukh <surajd.service@gmail.com>
Added VMware Cloud PKS and Cloud Foundry Container Runtime to places within the document that are correctly represented for Cloud and on-primises offerings and tooling. I also properly alphabetized the list.
Signed-off-by: Kendrick Coleman <kendrickc@vmware.com>
* Updated pick-right-solution.md with Docker Enterprise
Added Docker commercial and community products to the list of solutions for running Kubernetes including Docker Desktop and Docker Enterprise.
* Fix Docker Desktop entry in pick-right-solution.md
The words "Docker Desktop" was duplicated in the description under locally-hosted solutions.
* Updated pick-right-solution.md with Docker solutions
Added line wraps at 80 characters and changed containerizing to "deploying in containers" to make it more new-user friendly.
* Updated pick-right-solution.md
modified wrapping of first line to not break hyphenated word.
* adding feature state snip
Adding in the feature state to indicate when this feature was introduced.
* adding in "stable"
Didn't know it defaulted to alpha.
Himanshu Pandey