vbatts/cri-o
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Fix references to CRI-O

Browse source 
Signed-off-by: Daniel J Walsh <dwalsh@redhat.com>
This commit is contained in:
Daniel J Walsh 2017-10-13 13:43:43 -04:00
parent 5b62041194
commit 4e126d7798
5 changed files with 33 additions and 33 deletions
Download patch file Download diff file Expand all files Collapse all files

8
kubernetes.md
View file

@ -1,6 +1,6 @@
# Running cri-o on kubernetes cluster
# Running CRI-O on kubernetes cluster
## Switching runtime from docker to cri-o
## Switching runtime from docker to CRI-O
In standard docker kubernetes cluster, kubelet is running on each node as systemd service and is taking care of communication between runtime and api service.
It is reponsible for starting microservices pods (such as `kube-proxy`, `kubedns`, etc. - they can be different for various ways of deploying k8s) and user pods.
@ -9,7 +9,7 @@ Configuration of kubelet determines which runtime is used and in what way.
Kubelet itself is executed in docker container (as we can see in `kubelet.service`), but, what is important, **it's not** a kubernetes pod (at least for now),
so we can keep kubelet running inside container (as well as directly on the host), and regardless of this, run pods in chosen runtime.
Below, you can find an instruction how to switch one or more nodes on running kubernetes cluster from docker to cri-o.
Below, you can find an instruction how to switch one or more nodes on running kubernetes cluster from docker to CRI-O.
### Preparing crio
@ -95,7 +95,7 @@ If your cluster is using flannel network, your network configuration should be l
```
Then, kubelet will take parameters from `/run/flannel/subnet.env` - file generated by flannel kubelet microservice.
## Starting kubelet with cri-o
## Starting kubelet with CRI-O
Start crio first, then kubelet. If you created `crio` service:
```
# systemctl start crio