mirror of https://github.com/k3s-io/k3s
82d35fb461
The admission controller adds a default class to PVCs that do not require any specific class. This way, users (=PVC authors) do not need to care about storage classes, administrator can configure a default one and all these PVCs that do not care about class will get the default one. |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| README.md | ||
| config-default.sh | ||
| config-test.sh | ||
| coreos.xml | ||
| forShellEval.sed | ||
| namespace.yaml | ||
| network_kubernetes_global.xml | ||
| network_kubernetes_pods.xml | ||
| node-openssl.cnf | ||
| openssl.cnf | ||
| user_data.yml | ||
| user_data_master.yml | ||
| user_data_minion.yml | ||
| util.sh | ||
README.md
Kubernetes CoreOS cluster
With this tutorial one creates a Kubernetes CoreOS cluster containing of one
master and three minions (workers) running on 192.168.10.1-192.168.10.4.
For working correctly you need to create the directory addressed as POOL_PATH in
util.sh:
$ sudo mkdir /var/lib/libvirt/images/kubernetes
$ sudo chown -R $USER:$USER /var/lib/libvirt/images/kubernetes/
Then we follow the instructions in the main kubernetes directory.
For debugging set export UTIL_SH_DEBUG=1.
$ export KUBERNETES_PROVIDER=libvirt-coreos
$ make release-skip-tests
$ ./cluster/kube-up.sh
To bring the cluster down again, execute:
$ ./cluster/kube-down.sh
Have fun!