Kubernetes/Google GKE - Revision history

Pio2pio: /* Checking available and default versions */

2022-06-23T12:47:41Z

Checking available and default versions

← Older revision		Revision as of 14:47, 23 June 2022
Line 16:		Line 16:
	== Checking available and default versions ==		== Checking available and default versions ==
	<source lang=bash>		<source lang=bash>
			# Option 1
	CLUSTER_NAME=cluster-1		CLUSTER_NAME=cluster-1
	GKE_REGION=$(gcloud container clusters list --filter="name:${CLUSTER_NAME}" --format="value(location)")		GKE_REGION=$(gcloud container clusters list --filter="name:${CLUSTER_NAME}" --format="value(location)")
Line 21:		Line 22:
	# Check version: - index 0 (RAPID), 1 (REGULAR), 2 (STABLE)		# Check version: - index 0 (RAPID), 1 (REGULAR), 2 (STABLE)
	gcloud container get-server-config --region=$GKE_REGION --format="yaml(channels[1])" # skip format to obtain the full list		gcloud container get-server-config --region=$GKE_REGION --format="yaml(channels[1])" # skip format to obtain the full list

			# Option 2
			## Channel based versions

	CHANNEL=REGULAR # RAPID, STABLE		CHANNEL=REGULAR # RAPID, STABLE
	# Default version		### Default version
	gcloud container get-server-config --flatten="channels" --filter="channels.channel=${CHANNEL}" \		gcloud container get-server-config --flatten="channels" --filter="channels.channel=${CHANNEL}" \
	--format="yaml(channels.channel,channels.defaultVersion)"		--format="yaml(channels.channel,channels.defaultVersion)"

	# Available versions		### Available versions
	gcloud container get-server-config --flatten="channels" --filter="channels.channel=${CHANNEL}" \		gcloud container get-server-config --flatten="channels" --filter="channels.channel=${CHANNEL}" \
	--format="yaml(channels.channel,channels.validVersions)"		--format="yaml(channels.channel,channels.validVersions)"

	# No channel		## No channel - manual version selection
	## Default version		### Default version
	gcloud container get-server-config --format="yaml(defaultClusterVersion)"		gcloud container get-server-config --format="yaml(defaultClusterVersion)"

	## Available control plane versions		### Available control plane versions
	gcloud container get-server-config --format="yaml(validMasterVersions)"		gcloud container get-server-config --format="yaml(validMasterVersions)"

Pio2pio: /* Create a cluster */

2022-06-23T12:46:05Z

Create a cluster

← Older revision		Revision as of 14:46, 23 June 2022
Line 14:		Line 14:


	~~Get Kubernetes~~ available versions		== Checking available and default versions ==
	<source lang=bash>		<source lang=bash>
	CLUSTER_NAME=cluster-1		CLUSTER_NAME=cluster-1
	GKE_REGION=$(gcloud container clusters list --filter="name:${CLUSTER_NAME}" --format="value(location)")		GKE_REGION=$(gcloud container clusters list --filter="name:${CLUSTER_NAME}" --format="value(location)")
	# ~~Channels~~: 0 - RAPID, 1 - REGULAR, 2 - STABLE
			# Check version: - index 0 (RAPID), 1 (REGULAR), 2 (STABLE)
	gcloud container get-server-config --region=$GKE_REGION --format="yaml(channels[1])" # skip format to obtain the full list		gcloud container get-server-config --region=$GKE_REGION --format="yaml(channels[1])" # skip format to obtain the full list

	~~Fetching~~ server config ~~for europe~~-~~west1~~		CHANNEL=REGULAR # RAPID, STABLE
	channels:		# Default version
	- ~~null~~		gcloud container get-server-config --flatten="channels" --filter="channels.channel=${CHANNEL}" \
	- channel~~: REGULAR~~		--format="yaml(channels.channel,channels.defaultVersion)"
	~~defaultVersion: 1~~.21.~~5-gke.1302~~
	~~validVersions:~~		# Available versions
	- ~~1.21.5~~-~~gke~~.~~1802~~		gcloud container get-server-config --flatten="channels" --filter="channels.channel=${CHANNEL}" \
	- 1.21.5-~~gke.1302~~		--format="yaml(channels.channel,channels.validVersions)"
	- ~~1.20.12~~-~~gke.1500~~
	- ~~1.20.11~~-~~gke.1801~~		# No channel
			## Default version
			gcloud container get-server-config --format="yaml(defaultClusterVersion)"

			## Available control plane versions
			gcloud container get-server-config --format="yaml(validMasterVersions)"

			## Available node versions
			gcloud container get-server-config --format="yaml(validNodeVersions)"
	</source>		</source>

Pio2pio: /* Kortana Lens - metrics not showing from GKE Private cluster */

2022-02-16T10:39:28Z

Kortana Lens - metrics not showing from GKE Private cluster

← Older revision		Revision as of 12:39, 16 February 2022
Line 171:		Line 171:

	= Kortana Lens - metrics not showing from GKE Private cluster =		= Kortana Lens - metrics not showing from GKE Private cluster =
			When you are on Kortana Lens, it monitoring/observibility dashboards do run Prometheus discovery over `kubectl` then the same way they access prometheus:9090 endpoint. The communication is:
			Lens -> api-server (masters) [gke-masters-vpc] -over-gke-peerlink-> prometheus pods directly@TCP:9090[gke-node-pools]


			By default, firewall rules restrict your cluster control plane to only initiate TCP connections to your nodes and Pods on ports 443 (HTTPS) and 10250 (kubelet). The allowed ports (443 and 10250) refer to the ports exposed by your nodes and Pods, not the ports exposed by any Kubernetes services.
	* https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters#add_firewall_rules		* https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters#add_firewall_rules
	* https://github.com/kubernetes/kubernetes/issues/79739		* https://github.com/kubernetes/kubernetes/issues/79739
	* [https://cloud.google.com/kubernetes-engine/docs/concepts/firewall-rules Automatically created GKE Firewall Rules]		* [https://cloud.google.com/kubernetes-engine/docs/concepts/firewall-rules Automatically created GKE Firewall Rules]
	By default, firewall rules restrict your cluster control plane to only initiate TCP connections to your nodes and Pods on ports 443 (HTTPS) and 10250 (kubelet). The allowed ports (443 and 10250) refer to the ports exposed by your nodes and Pods, not the ports exposed by any Kubernetes services.

Pio2pio: /* Kortana Lens - metrics not showing from GKE Private cluster */

2022-02-16T07:32:15Z

Kortana Lens - metrics not showing from GKE Private cluster

← Older revision		Revision as of 09:32, 16 February 2022
Line 170:		Line 170:
	</source>		</source>

	= Kortana Lens - metrics not showing from GKE Private cluster =		= Kortana Lens - metrics not showing from GKE Private cluster =
			* https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters#add_firewall_rules
			* https://github.com/kubernetes/kubernetes/issues/79739
			* [https://cloud.google.com/kubernetes-engine/docs/concepts/firewall-rules Automatically created GKE Firewall Rules]
			By default, firewall rules restrict your cluster control plane to only initiate TCP connections to your nodes and Pods on ports 443 (HTTPS) and 10250 (kubelet). The allowed ports (443 and 10250) refer to the ports exposed by your nodes and Pods, not the ports exposed by any Kubernetes services.


			Lens issue
	* https://github.com/lensapp/lens/issues/1731#issuecomment-779196430		* https://github.com/lensapp/lens/issues/1731#issuecomment-779196430
	* https://istio.io/latest/docs/setup/platform-setup/gke/		* https://istio.io/latest/docs/setup/platform-setup/gke/

Pio2pio: /* References */

2022-02-15T13:26:42Z

References

@@ Line 168: / Line 168: @@
        --clusterrole cluster-admin \
        --user $(gcloud config get-value account)
 </source>
 = References =

Pio2pio: /* Create a cluster */

2021-12-31T11:59:40Z

Create a cluster

← Older revision		Revision as of 13:59, 31 December 2021
Line 11:		Line 11:
	NAME LOCATION MASTER_VERSION MASTER_IP MACHINE_TYPE NODE_VERSION NUM_NODES STATUS		NAME LOCATION MASTER_VERSION MASTER_IP MACHINE_TYPE NODE_VERSION NUM_NODES STATUS
	cluster-1 europe-west1-b 1.13.7-gke.8 35.205.145.199 n1-standard-1 1.13.7-gke.8 3 RUNNING		cluster-1 europe-west1-b 1.13.7-gke.8 35.205.145.199 n1-standard-1 1.13.7-gke.8 3 RUNNING
			</source>

	#~~Free up some resources~~
	~~watch~~ -~~d kubectl get pods~~ --~~all~~-~~namespaces~~		Get Kubernetes available versions
	~~kubectl~~ -~~n kube~~-~~system scale~~ --~~replicas=0 deployment/kube~~-~~dns~~-~~autoscaler~~		<source lang=bash>
	~~kubectl~~ -~~n kube~~-~~system scale~~ --~~replicas=~~1 ~~deployment/kube~~-~~dns~~		CLUSTER_NAME=cluster-1
			GKE_REGION=$(gcloud container clusters list --filter="name:${CLUSTER_NAME}" --format="value(location)")
			# Channels: 0 - RAPID, 1 - REGULAR, 2 - STABLE
			gcloud container get-server-config --region=$GKE_REGION --format="yaml(channels[1])" # skip format to obtain the full list

			Fetching server config for europe-west1
			channels:
			- null
			- channel: REGULAR
			defaultVersion: 1.21.5-gke.1302
			validVersions:
			- 1.21.5-gke.1802
			- 1.21.5-gke.1302
			- 1.20.12-gke.1500
			- 1.20.11-gke.1801
	</source>		</source>

Pio2pio: /* Cluster commands */

2021-12-31T11:51:59Z

Cluster commands

← Older revision		Revision as of 13:51, 31 December 2021
Line 102:		Line 102:


	Cluster		Cluster update
	<source lang=bash>		<source lang=bash>
	gcloud container clusters update cluster-2 --enable-autoscaling --node-pool=default-pool --min-nodes=3 --max-nodes=5 \		gcloud container clusters update cluster-2 --enable-autoscaling --node-pool=default-pool --min-nodes=3 --max-nodes=5 \

Pio2pio: /* Create a cluster */

2020-11-21T14:38:12Z

Create a cluster

← Older revision		Revision as of 16:38, 21 November 2020
Line 8:		Line 8:
	--region europe-west1-b --username=admin cluster-1		--region europe-west1-b --username=admin cluster-1
	# ----cluster-ipv4-cidr ...		# ----cluster-ipv4-cidr ...
	~~WARNING: In June 2019, node auto-upgrade will be enabled by default for newly created clusters and node pools. To disable it, use the `--no-enable-autoupgrade` flag.~~
	WARNING: Starting in 1.12, default node pools in new clusters will have their legacy Compute Engine instance metadata endpoints disabled by default. To create a cluster with legacy instance metadata endpoints disabled in the default node pool, run `clusters create` with the flag `--metadata disable-legacy-endpoints=true`.
	WARNING: The Pod address range limits the maximum size of the cluster. Please refer to https://cloud.google.com/kubernetes-engine/docs/how-to/flexible-pod-cidr to learn how to optimize IP address allocation.
	~~This will disable the autorepair feature for nodes. Please see https://cloud.google.com/kubernetes-engine/docs/node-auto-repair for more information on node autorepairs.~~
	~~Creating cluster cluster-1 in europe-west1-b... Cluster is being health-checked (master is healthy)...done.~~
	~~Created [https://container.googleapis.com/v1/projects/responsive-sun-*****/zones/europe-west1-b/clusters/cluster-1].~~
	To inspect the contents of your cluster, go to: https://console.cloud.google.com/kubernetes/workload_/gcloud/europe-west1-b/cluster-1?project=responsive-sun-*****
	~~kubeconfig entry generated for cluster-1.~~

	NAME LOCATION MASTER_VERSION MASTER_IP MACHINE_TYPE NODE_VERSION NUM_NODES STATUS		NAME LOCATION MASTER_VERSION MASTER_IP MACHINE_TYPE NODE_VERSION NUM_NODES STATUS

Pio2pio: /* Cluster commands */

2020-01-30T08:53:44Z

Cluster commands

← Older revision		Revision as of 10:53, 30 January 2020
Line 106:		Line 106:

	$> gcloud compute disks list mongo-disk # old syntax, still working as of 29/01/2020		$> gcloud compute disks list mongo-disk # old syntax, still working as of 29/01/2020
			</source>



			Cluster
			<source lang=bash>
			gcloud container clusters update cluster-2 --enable-autoscaling --node-pool=default-pool --min-nodes=3 --max-nodes=5 \
			# [--zone [COMPUTE_ZONE] --project [PROJECT_ID]]

			# Disable autoscaling if you want to scale to zero as otherwise it may have undesirabel effects
			gcloud container clusters update cluster-2 --no-enable-autoscaling --node-pool=default-pool

			gcloud container clusters resize [CLUSTER_NAME] --node-pool [POOL_NAME] --num-nodes [NUM_NODES]
	</source>		</source>

Pio2pio: /* Cluster commands */

2020-01-29T09:00:22Z

Cluster commands

@@ Line 53: / Line 53: @@
 gcloud container clusters describe cluster-1
 gcloud container clusters delete   cluster-1
 </source>