Advertisement
drpanwe

Untitled

Aug 13th, 2018
177
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.79 KB | None | 0 0
  1. zypper ar -f https://download.opensuse.org/repositories/devel:/kubic/openSUSE_Tumbleweed/devel:kubic.repo
  2. zypper ref
  3. transactional-update pkg install -f kubernetes-kubeadm
  4. reboot
  5.  
  6. # Fix https://github.com/kubernetes/kubernetes/issues/56850
  7. cat /etc/sysconfig/kubelet
  8. KUBELET_EXTRA_ARGS="--runtime-cgroups=/systemd/system.slice --kubelet-cgroups=/systemd/system.slice"
  9.  
  10. # Start kubeadm
  11. kubeadm init
  12. or
  13. kubeadm init --node-name=linux-uwkw.fritz.box # Use the FQDN hostname
  14.  
  15. # CoreDNS is now not running (it requires a plugin)
  16.  
  17. # Install network plugin (Weavenet)
  18. kubectl apply -f "https://cloud.weave.works/k8s/net?k8s-version=$(kubectl version | base64 | tr -d '\n')"
  19.  
  20. # CoreDNS STILL NOT RUNNING ...
  21.  
  22. # We miss CNI binaries?
  23. # From Kubelet: Error while adding to cni lo network: failed to find plugin "loopback" in path [/opt/cni/bin]
  24. # cat /var/lib/kubelet/kubeadm-flags.env
  25. -> KUBELET_KUBEADM_ARGS=--cgroup-driver=cgroupfs --cni-bin-dir=/opt/cni/bin --cni-conf-dir=/etc/cni/net.d --network-plugin=cni
  26. cd /opt/cni/bin
  27. curl -L -O https://github.com/containernetworking/plugins/releases/download/v0.7.1/cni-plugins-amd64-v0.7.1.tgz
  28. tar -xf cni-plugins-amd64-v0.7.1.tgz
  29.  
  30. ** NOTICE**
  31. # In case you have installed Flannel, you need to start kubeadm like this:
  32. kubeadm init --pod-network-cidr=10.244.0.0/16
  33.  
  34. # instead of Weavenet, then you need more CNI binary rather than just loopback.
  35. # These are: (bridge, flannel, host-local, loopback, portmap).
  36. # All of these are included in the compressed *.tgz archive.
  37.  
  38.  
  39. # Check the coredns is now running
  40.  
  41.  
  42. # Deploy Dashboard
  43. kubectl -n kube-system edit service kubernetes-dashboard
  44. Change type: ClusterIP to type: NodePort and save file. If it's already changed go to next step.
  45. Next we need to check port on which Dashboard was exposed. (See TCP Ports)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement