my KIND configurations for different practices
CKA, CKAD and CKS test environment support calico and flannel. The KIND cluster configrations will be added first.
-
[*] kustomize
-
[*] jsonnet
-
[*] tanka
-
[*] jsonnet-bundler
-
[*] helm
-
[] kubecfg
-
[*] telepresence
-
[*] skaffold
-
[*] tilt
-
[*] Service catalog
-
[*] Istio : Fundamentals for Istio by Solo.io, Intermediate for Istio by Solo.io, Fundamentals for Istio Ambient Mesh by Solo.io
-
[*] envoyproxy: Envoy Fundamentals, Fundamentals for Envoy by Solo.io
-
database
-
[*] mysql operator
-
[] postgresql
-
[] ClickHouse
-
-
Security
-
[] App Armor
-
[*] Calico: CERTIFIED CALICO OPERATOR: LEVEL 1, CERTIFIED CALICO OPERATOR: AWS EXPERT
-
[] hsm
-
[] Trivy
-
[] Sysdig
-
[] Falco
-
-
Certification management
-
[*] cert-managr
-
[*] Let’s Encrypt
-
[*] ACME webhook for GoDaddy: helm based
-
-
LMA stack: logging, monitoring and alerting
-
[*] ECK
-
[] logstash: elastic doesn’t provide logstash for k8s
-
[] Fluentd
-
[] alerting ?
-
-
application cicd
-
[*] argo-workflow
-
[] Progressive Delivery—argocd rollouts
-
[*] knative
-
[*] gitops argocd
-
[] tiggermesh
-
[*] tekton, Cloud Native CI/CD, used by knative and triggermesh
-
[*] fluxcd: one project one instance
-
-
Build
-
[*] bazel
-
[] Buck
-
[] BuildXL
-
-
Secret Management
-
[] secret management https://github.com/banzaicloud/bank-vaults
-
[*] sealed-secrets
-
[] External Secrets
-
[] Secrets Store CSI
-
-
Kubernetes cloud provider
-
[*] eksctl
-
[*] Alibaba Cloud Container Service for Kubernetes (ACK)
-
-
API gateway, Service Mesh
-
[*] mesh, basically istio now is the de facto standard.
-
-
AI, Big Data, Machine Learning
-
[] kubeflow: installation
-
Docker, kind, kinder, jq, yq, kustomize and helm are installed at your machine
#in wsl2 + docker, run following command before start docker service
sudo mkdir /sys/fs/cgroup/systemd
sudo mount -t cgroup -o none,name=systemd cgroup /sys/fs/cgroup/systemd
sudo service docker start
./up.sh [cluster-name]
up.sh will call kind with the cluster configuration to create the cluster if there isn’t kind clusters named kind. after the creation of the cluste, up.sh will call the corresponding hook script if it exists under ./configs folder.