Difference between revisions of "Initializing the Kubernetes cluster"
m (→Update kubelet configuration for master node) |
m (→Daemonsets) |
||
| Line 96: | Line 96: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
| − | == Daemonsets == | + | == Daemonsets on Master node == |
=== Flannel daemonset (pod network for communication) === | === Flannel daemonset (pod network for communication) === | ||
| + | |||
| + | <syntaxhighlight lang="bash"> | ||
| + | > cd init | ||
| + | > ./start_pod_network.sh | ||
| + | </syntaxhighlight> | ||
| + | |||
=== nVidia daemonset === | === nVidia daemonset === | ||
| + | <syntaxhighlight lang="bash"> | ||
| + | > cd init | ||
| + | > ./deploy_nvidia_device_plugin.sh | ||
| + | </syntaxhighlight> | ||
== Authentication systems == | == Authentication systems == | ||
Revision as of 15:28, 17 June 2019
Contents
Kubernetes and pre-requisites
Install Kubernetes on Ubuntu 18.04. Assuming version 1.14.2 is pulled, check how to fix version.
> cd init
> ./install_kubernetes.sh
Reconfigure docker runtime. Edit /etc/docker/daemon.json as follows:
{
"exec-opts": ["native.cgroupdriver=systemd"],
"log-driver": "json-file",
"log-opts": {
"max-size": "100m"
},
"storage-driver": "overlay2"
}
Restart docker daemon:
> mkdir -p /etc/systemd/system/docker.service.d
> systemctl daemon-reload
> systemctl restart docker
Make sure swap is off
> sudo swapoff -a
Check /etc/fstab if swap is still configured there, delete if this is the case.
Create cluster configuration scripts
OBSOLETE, DOES NOT SEEM TO WORK IN NEW KUBERNETES.
> cd init/templates
# edit cluster information in the following config file
> nano make_init_config.sh
> touch /home/kubernetes/.rnd
> ./make_init_config.sh
This will generate the init config from the config template and store it in /home/kubernetes/clusters/ccu.
Spin up the master node
Use kubeadm with vanilla defaults to initialize the control plane.
> sudo systemctl enable docker.service
> sudo kubeadm init
If this fails at any point, use kubeadm reset after problems have been fixed before trying to re-initialize.
- Post-init steps to setup admin user on this account
> cd init
> ./finalize_master.sh
Update kubelet configuration for master node
Edit /etc/kubernetes/manifests/kube-controller-manager.yaml:
spec:
containers:
- command:
# add these two
- --allocate-node-cidrs=true
- --cluster-cidr=10.244.0.0/16
Copy certs/ca.crt (certificate for ccu.uni-konstanz.de) to /usr/share/ca-certificates/ca-dex.pem.
Edit /etc/kubernetes/manifests/kube-apiserver.yaml:
spec:
containers:
- command:
# add these five
- --oidc-issuer-url=https://ccu.uni-konstanz.de:32000/dex
- --oidc-client-id=loginapp
- --oidc-ca-file=/usr/share/ca-certificates/ca-dex.pem
- --oidc-username-claim=name
- --oidc-groups-claim=groups
Daemonsets on Master node
Flannel daemonset (pod network for communication)
> cd init
> ./start_pod_network.sh
nVidia daemonset
> cd init
> ./deploy_nvidia_device_plugin.sh
Authentication systems
DEX with LDAP
TODO: outdated, switched to containerized DEX. Check what still needs to be done.
Set up according to this tutorial with customized install scripts in kubernetes/init/dex/
- Create secrets for TLS connections, use certs for ccu.uni-konstanz.de
- Modify ca-cm.yml to contain correct ca.
- Run upload_ccu_tls.sh
- Spin up login application service.
- Modify loginapp-cm.yml: server config
- Modify loginapp-ing-srv.yml: service data, mapping of ports to outside world
- Modify loginapp-deploy.yml: ID secret for TLS
- Run start-login-service.sh
- Spin up dex
- Modify dex-cm.yml: server data and LDAP configuration
- Modify dex-ing-srv.yml: service data, mapping of ports to outside world
- Modify dex-deploy.yml: ID secret for TLS
- Run start-dex-service.sh