mirror of
https://github.com/linuxkit/linuxkit.git
synced 2025-10-07 20:35:32 +00:00
b34aaee4db
Having described all the setup describing the acgual usage seems useful! Signed-off-by: Ian Campbell <ijc@docker.com>
99 lines
2.7 KiB
Markdown
99 lines
2.7 KiB
Markdown
# Kubernetes and LinuxKit
|
|
|
|
This project aims to demonstrate how one can create minimal and immutable Kubernetes OS images with LinuxKit.
|
|
|
|
Make sure to `cd projects/kubernetes` first.
|
|
|
|
Edit `kube-master.yml` and add your public SSH key to `files` section.
|
|
|
|
Build OS images:
|
|
```
|
|
make build-vm-images
|
|
```
|
|
|
|
Boot Kubernetes master OS image using `hyperkit` on macOS: or `qemu` on Linux:
|
|
```
|
|
./boot.sh
|
|
```
|
|
|
|
Get IP address of the master:
|
|
```
|
|
ip addr show dev eth0
|
|
```
|
|
|
|
Login to the kubelet container:
|
|
```
|
|
./ssh_into_kubelet.sh <master-ip>
|
|
```
|
|
|
|
Manually initialise master with `kubeadm`:
|
|
```
|
|
kubeadm-init.sh
|
|
```
|
|
|
|
Once `kubeadm` exits, make sure to copy the `kubeadm join` arguments,
|
|
and try `kubectl get nodes` from within the master.
|
|
|
|
If you just want to run a single node cluster with jobs running on the master, you can use:
|
|
```
|
|
kubectl taint nodes --all node-role.kubernetes.io/master- --kubeconfig /etc/kubernetes/admin.conf
|
|
```
|
|
|
|
To boot a node use:
|
|
```
|
|
./boot.sh <n> [<join_args> ...]
|
|
```
|
|
|
|
More specifically, to start 3 nodes use 3 separate shells and run this:
|
|
```
|
|
shell1> ./boot.sh 1 --token bb38c6.117e66eabbbce07d 192.168.65.22:6443
|
|
shell2> ./boot.sh 2 --token bb38c6.117e66eabbbce07d 192.168.65.22:6443
|
|
shell3> ./boot.sh 3 --token bb38c6.117e66eabbbce07d 192.168.65.22:6443
|
|
```
|
|
|
|
## Platform specific information
|
|
|
|
### MacOS
|
|
|
|
The above instructions should work as is.
|
|
|
|
### Linux
|
|
|
|
By default `linuxkit run` uses user mode networking which does not
|
|
support access from the host. To workaround this you can use port
|
|
forwarding e.g.
|
|
|
|
KUBE_RUN_ARGS="-publish 2222:22" ./boot.sh
|
|
|
|
ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -p 2222 root@localhost
|
|
|
|
However you will not be able to run worker nodes since individual
|
|
instances cannot see each other.
|
|
|
|
To enable networking between instance unfortunately requires `root`
|
|
privileges to configure a bridge and setup the bridge mode privileged
|
|
helper.
|
|
|
|
See http://wiki.qemu.org/Features/HelperNetworking for details in
|
|
brief you will need:
|
|
|
|
- To setup and configure a bridge (including e.g. DHCP etc) on the
|
|
host. (You can reuse a bridge created by e.g. `virt-mananger`)
|
|
- To set the `qemu-bridge-helper` setuid root. The location differs by
|
|
distro, it could be `/usr/lib/qemu/qemu-bridge-helper` or
|
|
`/usr/local/libexec/qemu-bridge-helper` or elsewhere. You need to
|
|
`chmod u+s «PATH»`.
|
|
- List the bridge created in the first step in `/etc/qemu/bridge.conf`
|
|
with a line like `allow br0` (if your bridge is called `br0`).
|
|
- Set `KUBE_NETWORKING=bridge,«name»` e.g.
|
|
|
|
KUBE_NETWORKING="bridge,br0" ./boot.sh
|
|
KUBE_NETWORKING="bridge,br0" ./boot.sh 1 «options»
|
|
|
|
## Configuration
|
|
|
|
The `boot.sh` script has various configuration variables at the top
|
|
which can be overridden via the environment e.g.
|
|
|
|
KUBE_VCPUS=4 ./boot.sh
|