GoLang, Go - Links

https://www.youtube.com/watch?v=yyUHQIec83I

https://www.youtube.com/watch?v=YS4e4q9oBaU

https://www.youtube.com/watch?v=1NF2LtWbA1g

https://go.dev/play/

https://go.dev/tour/

https://go.dev/docs

https://pkg.go.dev

https://gobyexample.com/

https://golangbot.com/

https://www.golangprograms.com/

EKCTL - Command Sheet - Cheat Code

https://eksctl.io/usage/unowned-clusters/

• Create:
  • eksctl create nodegroup (see note below)
  • eksctl create fargateprofile
  • eksctl create iamserviceaccount
  • eksctl create iamidentitymapping
• Get:
  • eksctl get clusters/cluster
  • eksctl get nodegroup
  • eksctl get labels
• Delete:
  • eksctl delete cluster
  • eksctl delete nodegroup
  • eksctl delete fargateprofile
  • eksctl delete iamserviceaccount
  • eksctl delete iamidentitymapping
• Upgrade:
  • eksctl upgrade cluster
  • eksctl upgrade nodegroup
• Set/Unset:
  • eksctl set labels
  • eksctl unset labels
• Scale:
  • eksctl scale nodegroup
• Drain:
  • eksctl drain nodegroup
• Enable:
  • eksctl enable profile
  • eksctl enable repo
• Utils:
  • eksctl utils associate-iam-oidc-provider
  • eksctl utils describe-stacks
  • eksctl utils install-vpc-controllers
  • eksctl utils nodegroup-health
  • eksctl utils set-public-access-cidrs
  • eksctl utils update-cluster-endpoints
  • eksctl utils update-cluster-logging
  • eksctl utils write-kubeconfig
  • eksctl utils update-coredns
  • eksctl utils update-aws-node
  • eksctl utils update-kube-proxy

Kubectl and EKSCTL - Story

• eksctl creates Cluster using Cloudformation template
• Cluster is mapped to EC2-Role and it here where we get visibility
• Each Cluster is mapped to  "Context" in ~/.kube/config File which is a config file used by kubectl
• kubectl knows what its target vms are or context is.
• Each Context/Target Nodes can be shared between many different Project by using "namespaces"

Kubectl Context Switch - Kubernetes

eksctl creates Cluster using Cloudformation template

Cluster is mapped to EC2-Role and it here where we get visibility

Each Cluster is mapped to  "Context" in ~/.kube/config File which is a config file used by kubectl

kubectl knows what its target vms are or context is.

Each Context/Target Nodes can be shared between many different Project by using "namespaces"

~\.kube\config

kubectl config get-contexts

kubectl config current-context

kubectl config use-context <context-name>

https://www.shellhacks.com/kubectl-switch-context-kubernetes/

https://www.shellhacks.com/kubectl-get-pods-list-all-pods-kubernetes/

=========================================================================

Kubectl - Multiple Eksctl contexts - Switch - How ??

https://stackoverflow.com/a/43661208/2413870

https://stackoverflow.com/questions/43643463/how-to-switch-kubectl-clusters-between-gcloud-and-minikube

You can switch from local (minikube) to gcloud and back with:

kubectl config use-context CONTEXT_NAME




to list all contexts:

kubectl config get-contexts




You can create different enviroments for local and gcloud and put it in separate yaml files.

https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/