homelab VS ingress-nginx

I do similar stuff but without windows https://gitlab.com/dekarl/homelab/-/blob/master/kubernetes-cluster.tf replace the maas stuff with hyperv

I do the configuration of my playground cluster like that. See https://gitlab.com/dekarl/homelab/-/tree/master/ (charts/configuration and helmfile-configuration)

My current homelab consists of amd64 thin clients, a NAS with MaaS and plain WiFi controlled power plugs. I'm still stuck at stateless workloads. Persistant volumes come after the Summer break.

I'm playing around with MaaS, too. Currently using microk8s, but looking for a replacement, like Talos.

Keeping the manifest updated should become a copypaste battle around now. Time to look into helmfile with one embedded chart for one handler and many instantiations. Start with one folder for the charts and two folders for the deployment to prod/stage. I started such a setup for my homelab at https://gitlab.com/dekarl/homelab/-/tree/master/

# Add NGINX ingress using Helm eks.HelmChart( self, "NginxIngress", cluster=cluster, chart="ingress-nginx", repository="https://kubernetes.github.io/ingress-nginx", namespace="ingress-nginx", values=helm_values )

ingress-nginx

The second one is a combination of tools: External DNS, cert-manager, and NGINX ingress. Using these as a stack, you can quickly deploy an application, making it available through a DNS with a TLS without much effort via simple annotations. When I first discovered External DNS, I was amazed at its quality.

resource "helm_release" "icrelease" { name = "nginx-ingress" repository = "https://kubernetes.github.io/ingress-nginx" chart = "ingress-nginx" version = "4.9.1" namespace = kubernetes_namespace.icnamespace.metadata[0].name set { name = "controller.ingressClassResource.default" value = "true" } }

helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx --namespace ingress-nginx --create-namespace -f custom/ghost/nginx.yaml

For example, if you chose Nginx Ingress, you will use some of its dozens of annotations that are not portable if you decide to switch to another Ingress implementation like Apache APISIX.

The controller is installed with helm upgrade --install ingress-nginx ingress-nginx --repo https://kubernetes.github.io/ingress-nginx --namespace ingress-nginx --create-namespace

helm repo add jetstack https://charts.jetstack.io helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo add rancher-latest https://releases.rancher.com/server-charts/latest helm repo update helm repo list

Everything in the YAML snippets below — except for ingress configuration — relates to configuring the NGINX ingress controller. This includes customizing the default configuration.