Pavan Madduri pmady

Helm CheatSheet

	# Namespace / Service
	- A pod can access a service in its own namespace by just using service name.
	A pod can access a service in a different namespace by using below format.
	<svc-name>.<ns-name>.<svc>.<cluster.local>
	e.g db-service.dev.svc.cluster.local
	- When a service is created, a DNS entry is added automatically in this format:
	db-service.dev.svc.cluster.local
	Here db-service is service name, dev is namespace, svc represents service and cluster.local is domain.

	CIDR Total Number Network Description:
	Notation: of addresses: Mask:
	--------------------------------------------------------------------
	/0 4,294,967,296 0.0.0.0 All Addresses
	/1 2,147,483,684 128.0.0.0 128 /8 networks
	/2 1,073,741,824 192.0.0.0 64 /8 networks
	/3 536,870,912 224.0.0.0 32 /8 networks
	/4 268,435,456 240.0.0.0 16 /8 networks
	/5 134,217,728 248.0.0.0 8 /8 networks
	/6 67,108,864 252.0.0.0 4 /8 networks

	git clone <remote-forked-repo>

	cd <repo-folder>

	git remote -v

	## Adding as upstream original repo **
	git remote add upstream <remote--original-repo>

	## Check status**

	# Delete all resources in namespace
	kubectl delete "$(kubectl api-resources --namespaced=true --verbs=delete -o name \| tr "\n" "," \| sed -e 's/,$//')" --all

	# remove the CRD finalizer blocking on custom resource cleanup
	kubectl patch crd/crontabs.stable.example.com -p '{"metadata":{"finalizers":[]}}' --type=merge

	cloud_user@lalit2109841c:~$ kubectl -h
	kubectl controls the Kubernetes cluster manager.

	Find more information at: https://kubernetes.io/docs/reference/kubectl/overview/


	CKAD
	*************************************************************************************************************
	Kubernetes API primitives:
	https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/

	Lesson Reference
	kubectl api-resources -o name

	kubectl get pods -n kube-system