Kubernetes/Install Master and nodes - Revision history

Pio2pio: /* References */

2019-10-16T07:25:58Z

References

@@ Line 315: / Line 315: @@
 sudo kuebadm join <IP>:6443 --token 123abc.abcabcabcabc --discovery-token-ca-cert-hash sha256:****
 </source>
 == References ==
 *[https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/ kubeadm upgrade] K8s docs

Pio2pio: /* Initialize a cluster */

2019-10-15T07:19:28Z

Initialize a cluster

← Older revision		Revision as of 09:19, 15 October 2019
Line 30:		Line 30:
	Run only on the master to initialize the cluster		Run only on the master to initialize the cluster
	<source lang=bash>		<source lang=bash>
	sudo kubeadm init --pod-network-cidr=10.100.0.0/16		sudo kubeadm init --pod-network-cidr=10.100.0.0/16 # flannel default is 10.244.0.0/16

	I0705 06:23:54.675905 24293 version.go:237] remote version is much newer: v1.15.0; falling back to: stable-1.13		I0705 06:23:54.675905 24293 version.go:237] remote version is much newer: v1.15.0; falling back to: stable-1.13
Line 109:		Line 109:


	Create Flannel CNI network overlay to allow nodes to communicate with each other		Create Flannel CNI network overlay to allow nodes to communicate with each other. Default flannel pod network is 10.244.0.0/16, you need to update manifest if this is not your cidr.
	<source lang=bash>		<source lang=bash>
	kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/bc79dd1505b0c8681ece4de4c0d86c5cd2643275/Documentation/kube-flannel.yml		kubectl apply -f https://raw.githubusercontent.com/coreos/flannel/bc79dd1505b0c8681ece4de4c0d86c5cd2643275/Documentation/kube-flannel.yml
Line 122:		Line 122:
	daemonset.extensions/kube-flannel-ds-s390x created		daemonset.extensions/kube-flannel-ds-s390x created
	</source>		</source>


	= Join worker nodes =		= Join worker nodes =

Pio2pio: /* Install binaries */

2019-10-15T07:10:03Z

Install binaries

← Older revision		Revision as of 09:10, 15 October 2019
Line 17:		Line 17:
	EOF		EOF

	#Install software		# Install software
	sudo apt-get update		sudo apt-get update
	sudo apt-get install -y docker-ce=18.06.1~ce~3-0~ubuntu kubelet=1.13.10-00 kubeadm=1.13.10-00 kubectl=1.13.10-00		sudo apt-get install -y docker-ce=18.06.1~ce~3-0~ubuntu kubelet=1.13.10-00 kubeadm=1.13.10-00 kubectl=1.13.10-00
	# Set packages at the current versions so they won't autoupdate		# Set packages at the current versions so they won't autoupdate
	sudo apt-mark hold docker-ce kubelet kubeadm kubectl		sudo apt-mark hold docker-ce kubelet kubeadm kubectl
	#~~Add the~~ iptables ~~rule to sysctl.conf;~~ then enable ~~imidiately~~		# Enable iptables bridge call, then enable immediately
	echo "net.bridge.bridge-nf-call-iptables=1" \| sudo tee -a /etc/sysctl.conf		echo "net.bridge.bridge-nf-call-iptables=1" \| sudo tee -a /etc/sysctl.conf
	sudo sysctl -p		sudo sysctl -p

Pio2pio: /* Install binaries */

2019-09-25T09:07:07Z

Install binaries

← Older revision		Revision as of 11:07, 25 September 2019
Line 1:		Line 1:
	This example is based on Ubuntu 16 LTS		This example is based on Ubuntu 16 LTS

			= Updates =
			* Updated version of Kubernetes binary to 1.13.10-00 to align with AWS version. The commands output haven't been reflected, but all worked.

	= Install binaries =		= Install binaries =

Pio2pio: /* Install binaries */

2019-09-25T08:42:36Z

Install binaries

← Older revision		Revision as of 10:42, 25 September 2019
Line 16:		Line 16:
	#Install software		#Install software
	sudo apt-get update		sudo apt-get update
	sudo apt-get install -y docker-ce=18.06.1~ce~3-0~ubuntu kubelet=1.13.5-00 kubeadm=1.13.5-00 kubectl=1.13.5-00		sudo apt-get install -y docker-ce=18.06.1~ce~3-0~ubuntu kubelet=1.13.10-00 kubeadm=1.13.10-00 kubectl=1.13.10-00
	# Set packages at the current versions so they won't autoupdate		# Set packages at the current versions so they won't autoupdate
	sudo apt-mark hold docker-ce kubelet kubeadm kubectl		sudo apt-mark hold docker-ce kubelet kubeadm kubectl

Pio2pio: /* Upgrade */

2019-07-11T07:47:24Z

Upgrade

← Older revision		Revision as of 09:47, 11 July 2019
Line 227:		Line 227:
	<code>kubeadm</code> allows us to upgrade a cluster components in controlled smart way it means the upgrade process will verify what components can be upgraded. Output examples are based on Amazon EKS, but EKS does not allow access for Control Place access, thus cannot see API Server or kube-controller.		<code>kubeadm</code> allows us to upgrade a cluster components in controlled smart way it means the upgrade process will verify what components can be upgraded. Output examples are based on Amazon EKS, but EKS does not allow access for Control Place access, thus cannot see API Server or kube-controller.
	<source lang=bash>		<source lang=bash>
	#kubectl version --short #check version for a API client (kubelet) and API server		#Verify different components versions
			kubectl version --short #check version for a API client (kubelet) and API server
	Client Version: v1.15.0		Client Version: v1.15.0
	Server Version: v1.12.6-eks-d69f1b		Server Version: v1.12.6-eks-d69f1b

	kubectl get pods -n kube-system kube-controller-manager-<podUID> -o yaml #version of the scheduler and controller manager		kubectl get pods -n kube-system kube-controller-manager-<podUID> -o yaml \|grep image: #version of the scheduler and controller manager
			image: k8s.gcr.io/kube-controller-manager:v1.12.10
			image: k8s.gcr.io/kube-controller-manager:v1.12.10
	kubectl get pods -n kube-system #kube-controller pod		kubectl get pods -n kube-system #kube-controller pod

	#Set the VERSION and ARCH you want to upgrade to		#Set the VERSION and ARCH you want to upgrade to
	export VERSION=v1.14.1; export ARCH=amd64		export VERSION=v1.13.8; export ARCH=amd64

	#Download Kubernetes binaries		#Download Kubernetes binaries
Line 243:		Line 246:
	sudo kubeadm version		sudo kubeadm version
	sudo kubeadm upgrade plan #plan upgrade		sudo kubeadm upgrade plan #plan upgrade
	kubeadm upgrade ~~apply~~ v1.14.1 ~~#apply~~ upgrade		[preflight] Running pre-flight checks.
			[upgrade] Making sure the cluster is healthy:
			[upgrade/config] Making sure the configuration is correct:
			[upgrade/config] Reading configuration from the cluster...
			[upgrade/config] FYI: You can look at this config file with 'kubectl -n kube-system get cm kubeadm-config -oyaml'
			[upgrade] Fetching available versions to upgrade to
			[upgrade/versions] Cluster version: v1.12.10
			[upgrade/versions] kubeadm version: v1.13.8
			I0711 07:32:05.071864 17589 version.go:237] remote version is much newer: v1.15.0; falling back to: stable-1.13
			[upgrade/versions] Latest stable version: v1.13.8
			[upgrade/versions] Latest version in the v1.12 series: v1.12.10

	#~~Check~~ differences between the old and new manifests:		Components that must be upgraded manually after you have upgraded the control plane with 'kubeadm upgrade apply':
	~~diff kube-controller-manager.yaml~~ /etc/kubernetes/manifests/kube-controller-manager.yaml		COMPONENT CURRENT AVAILABLE
			Kubelet 3 x v1.12.2 v1.13.8

			Upgrade to the latest stable version:

			COMPONENT CURRENT AVAILABLE
			API Server v1.12.10 v1.13.8
			Controller Manager v1.12.10 v1.13.8
			Scheduler v1.12.10 v1.13.8
			Kube Proxy v1.12.10 v1.13.8
			CoreDNS 1.2.2 1.2.6
			Etcd 3.2.24 3.2.24

			You can now apply the upgrade by executing the following command:

			kubeadm upgrade apply v1.13.8

			#Upgrade
			kubeadm upgrade apply v1.13.8 #apply upgrade

			#You can check differences between the old and new manifests if you got it saved before upgrade
			sudo vi /etc/kubernetes/manifests/kube-controller-manager.yaml #current

	#Download the latest version of kubelet:		#Download the latest version of kubelet:
Line 253:		Line 287:
	sudo systemctl restart kubelet.service #restart is required		sudo systemctl restart kubelet.service #restart is required
	kubectl get nodes -w #check nodes versions		kubectl get nodes -w #check nodes versions

			#Upgrade version of kubelet on all worker nodes now
	</source>		</source>

Line 259:		Line 295:
	* so upgrading a node, you should check pod running on it, then evict them		* so upgrading a node, you should check pod running on it, then evict them
	<source lang=bash>		<source lang=bash>
	kubectl drain <node> --ignore-~~deamonsets~~		kubectl drain <node> --ignore-daemonsets
	kubectl get nodes #the drained node will be in 'Ready,SchedulingDisabled' status		kubectl get nodes #the drained node will be in 'Ready,SchedulingDisabled' status
	#the node now can be upgraded		#the node now can be upgraded

Pio2pio: /* Upgrade */

2019-07-10T07:51:15Z

Upgrade

@@ Line 253: / Line 253: @@
 sudo systemctl restart kubelet.service #restart is required
 kubectl get nodes -w #check nodes versions
 </source>
 == References ==
 *[https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/ kubeadm upgrade] K8s docs
 = References =

Pio2pio: /* Upgrade */

2019-07-10T07:15:07Z

Upgrade

← Older revision		Revision as of 09:15, 10 July 2019
Line 253:		Line 253:
	sudo systemctl restart kubelet.service #restart is required		sudo systemctl restart kubelet.service #restart is required
	kubectl get nodes -w #check nodes versions		kubectl get nodes -w #check nodes versions
			</source>
			== References ==
			*[https://kubernetes.io/docs/reference/setup-tools/kubeadm/kubeadm-upgrade/ kubeadm upgrade] K8s docs

	= References =		= References =

Pio2pio: /* References */

2019-07-10T07:14:05Z

References

@@ Line 223: / Line 223: @@
 kubectl describe nodes
 </source>
 = References =

Pio2pio: /* Testing cluster end-to-end */

2019-07-07T07:39:23Z

Testing cluster end-to-end

← Older revision		Revision as of 09:39, 7 July 2019
Line 209:		Line 209:
	#Check a response from the service		#Check a response from the service
	curl -I localhost:$node_port #run on a worker node		curl -I localhost:$node_port #run on a worker node
			HTTP/1.1 200 OK
			Server: nginx/1.17.1
			Date: Sun, 07 Jul 2019 07:36:00 GMT
			Content-Type: text/html
			Content-Length: 612
			Last-Modified: Tue, 25 Jun 2019 12:19:45 GMT
			Connection: keep-alive
			ETag: "5d121161-264"
			Accept-Ranges: bytes

	#Check information about nodes		#Check information about nodes