Kubernetes/Cluster - Revision history

Kenneth at 22:04, 22 December 2023

2023-12-22T22:04:22Z

← Older revision		Revision as of 22:04, 22 December 2023
Line 1:		Line 1:
			<!-- == Subpage Table of Contents == -->

			'''Subpage Table of Contents'''
			{{Special:PrefixIndex/{{PAGENAME}}/}}

			<br/>

	== Create Cluster ==		== Create Cluster ==

2023-12-22T17:59:18Z

Test Pod

← Older revision		Revision as of 17:59, 22 December 2023
Line 214:		Line 214:
	--discovery-token-ca-cert-hash sha256:4xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx		--discovery-token-ca-cert-hash sha256:4xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

	== Test ~~Pod~~ ==		== Test a few pods ==

	kubectl run shell1 --image ubuntu sleep infinity		kubectl run shell1 --image ubuntu sleep infinity
			kubectl run shell2 --image ubuntu sleep infinity
			kubectl run shell3 --image ubuntu sleep infinity
			kubectl run shell4 --image ubuntu sleep infinity
			kubectl run shell5 --image ubuntu sleep infinity

	== Delete Node ==		== Delete Node ==

2023-12-22T17:51:11Z

Join Nodes

← Older revision		Revision as of 17:51, 22 December 2023
Line 205:		Line 205:
	https://github.com/flannel-io/flannel#deploying-flannel-manually		https://github.com/flannel-io/flannel#deploying-flannel-manually

	== Join Nodes ==		== Join Worker Nodes ==

	1. Disable Swap		1. Disable Swap
Line 213:		Line 213:
	kubeadm join 192.x.x.x:6443 --token exxxxxxx.xxxxxxxxxxxx \		kubeadm join 192.x.x.x:6443 --token exxxxxxx.xxxxxxxxxxxx \
	--discovery-token-ca-cert-hash sha256:4xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx		--discovery-token-ca-cert-hash sha256:4xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

			== Test Pod ==

			kubectl run shell1 --image ubuntu sleep infinity

	== Delete Node ==		== Delete Node ==

2023-12-22T17:49:20Z

Initalize Pod Network - Flannel

← Older revision		Revision as of 17:49, 22 December 2023
Line 197:		Line 197:
	Note, if you need to retry, you can delete, then retry:		Note, if you need to retry, you can delete, then retry:
	kubectl delete -f https://github.com/flannel-io/flannel/releases/latest/download/kube-flannel.yml		kubectl delete -f https://github.com/flannel-io/flannel/releases/latest/download/kube-flannel.yml

			Note, flannel expects the CIDR to be 10.244.0.0/16. If you have it set to something else, you will need to modify the manifest. To check what your cluster is configured for, or if you even specified the the cidr during cluster creation (required for Flannel, if it returns nothing that is a problem): <ref>https://devops.stackexchange.com/questions/5898/how-to-get-kubernetes-pod-network-cidr</ref>
			kubectl cluster-info dump \| grep cluster-cidr

	reference:		reference:

2023-12-22T01:52:53Z

Get Join Command

← Older revision		Revision as of 01:52, 22 December 2023
Line 172:		Line 172:

	== Get Join Command ==		== Get Join Command ==

			kubeadm init phase upload-certs --upload-certs

	kubeadm token create --print-join-command		kubeadm token create --print-join-command

2023-12-21T23:00:10Z

Initalize with Docker

← Older revision		Revision as of 23:00, 21 December 2023
Line 135:		Line 135:
	Or Initalize cluster with Docker:		Or Initalize cluster with Docker:
	sudo kubeadm init --pod-network-cidr=10.244.0.0/16 --cri-socket=unix:///var/run/cri-dockerd.sock		sudo kubeadm init --pod-network-cidr=10.244.0.0/16 --cri-socket=unix:///var/run/cri-dockerd.sock

			=== Initalize with Redundant Control Plane ===

			sudo kubeadm init --pod-network-cidr=10.244.0.0/16 --control-plane-endpoint=192.x.x.x:6443 --upload-certs --cri-socket=unix:///var/run/cri-dockerd.sock

			With keepalived on same host:
			sudo kubeadm init --pod-network-cidr=10.244.0.0/16 --control-plane-endpoint=192.x.x.x:26443 --upload-certs --cri-socket=unix:///var/run/cri-dockerd.sock

	== Initalized Success ==		== Initalized Success ==

2023-12-20T17:32:27Z

Tear Down Cluster

← Older revision		Revision as of 17:32, 20 December 2023
Line 365:		Line 365:
	sudo kubeadm init --cri-socket=unix:///var/run/cri-dockerd.sock		sudo kubeadm init --cri-socket=unix:///var/run/cri-dockerd.sock

	== Tear Down ~~Cluster~~ ==		== Tear Down ==

	If you need to ~~try again~~:		If you need to reset a node (even controller) locally:
	kubeadm reset		kubeadm reset

	~~Sort of, this doesn't do a great job..~~.		If with docker:
			kubeadm reset --cri-socket=unix:///var/run/cri-dockerd.sock

	== Useful Debug ==		== Useful Debug ==

2023-12-20T17:31:25Z

Get Join Command

← Older revision		Revision as of 17:31, 20 December 2023
Line 170:		Line 170:
	Example:		Example:
	kubeadm join 192.x.x.x:6443 --token xxx.xxxxxxx --discovery-token-ca-cert-hash sha256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx		kubeadm join 192.x.x.x:6443 --token xxx.xxxxxxx --discovery-token-ca-cert-hash sha256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

			Example with Docker:
			kubeadm join 192.x.x.x:6443 --token xxx.xxxxxxx --discovery-token-ca-cert-hash sha256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx --cri-socket=unix:///var/run/cri-dockerd.sock

	== Initalize Pod Network - Flannel ==		== Initalize Pod Network - Flannel ==

2023-12-20T17:12:06Z

Get Join Command

← Older revision		Revision as of 17:12, 20 December 2023
Line 169:		Line 169:

	Example:		Example:
	kubeadm join 192.x.x.x:6443 --token xxx.xxxxxxx --discovery-token-ca-cert-hash sha256:~~b537xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx~~		kubeadm join 192.x.x.x:6443 --token xxx.xxxxxxx --discovery-token-ca-cert-hash sha256:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

	== Initalize Pod Network - Flannel ==		== Initalize Pod Network - Flannel ==

2023-12-20T17:11:45Z

Initalized Success

← Older revision		Revision as of 17:11, 20 December 2023
Line 163:		Line 163:

	WARNING WARNING WARNING - before joining another node, make sure to add your pod network!		WARNING WARNING WARNING - before joining another node, make sure to add your pod network!

			== Get Join Command ==

			kubeadm token create --print-join-command

			Example:
			kubeadm join 192.x.x.x:6443 --token xxx.xxxxxxx --discovery-token-ca-cert-hash sha256:b537xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

	== Initalize Pod Network - Flannel ==		== Initalize Pod Network - Flannel ==