Sebastian Mark
06b036ec71
- replace k0s with k3s in docker-compose.yml
- remove k0s-config.yaml
- remove metallb-address-pool
- update .renovaterc.json to match new file structure
- add new argocd-init files for k3s
- update README to reflect changes
🤖
|
||
|---|---|---|
| _templates | ||
| argocd-init | ||
| bin | ||
| manifests | ||
| .gitignore | ||
| .renovaterc.json | ||
| docker-compose.yml | ||
| logo.png | ||
| README.md | ||
k3s Kubernetes + Baseline
- k3s
- ArgoCD
- NGINX Ingress Controller
- cert-manager
- selfsigned issuer
- LetsEncrypt issuers (Prod and Staging)
- zabbix-proxy
- keel
- reloader
Run (k3s + baseline)
docker compose up
Get kubeconfig
docker compose exec -it k3s kubectl config view --flatten
Notes
ArgoCD
To retrieve the initial admin password use
kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d
To change the password follow Argocd account update password.
Linode
PROXY protocol needs to be enabled for ingress-nginx to see the clients IP in ingress log.
Add the PROXY protocol annotation to the ingress-nginx service:
annotations:
service.beta.kubernetes.io/linode-loadbalancer-proxy-protocol: v2
Update the ingress-nginx ConfigMap to make nginx expect PROXY protocol data:
data:
use-proxy-protocol: "true"
cert-manager
However, when you have the PROXY protocol enabled, the external load balancer does modify the traffic, prepending the PROXY line before each TCP connection. If you connect directly to the web server internally, bypassing the external load balancer, then it will receive traffic without the PROXY line.
This is particularly a problem when using cert-manager for provisioning SSL certificates.
After enabling the PROXY protocol cert-manager is unable to perform a self check ("propagation check failed", "failed to perform self check GET request").
hairpin-proxy adds PROXY protocol support for internal-to-LoadBalancer traffic for Kubernetes Ingress users, specifically for cert-manager self-checks (no further configuration needed).