2 Commits

Include renames

Author	SHA1	Message	Date
volker.raschekandCopilot	e17a4e7a7b	refactor(ingress)!: skip the Ingress when the HTTP Service is disabled ... An Ingress that points at a Service which the chart does not render is broken by definition: the backend reference cannot resolve and the ingress controller reports the rule as unavailable. The render condition therefore now also requires `service.http.enabled` and lives in the new `gitea.ingress.enabled` helper, so the same rule can be reused by other templates instead of being duplicated. The namespace is taken from `.Release.Namespace` again. The `namespace` value is not a documented chart parameter, and letting a single resource opt out of the release namespace breaks `helm uninstall` and Argo CD pruning, because neither tracks objects outside the release namespace. The `ingress.className` default changes from an empty string to `nginx`. An empty class makes the cluster fall back to the default IngressClass, which silently produces a different result per cluster; naming the controller the chart is tested against makes the rendered output predictable. The scattered ingress suites are consolidated into a single `unittests/helm/ingress/ingress.yaml` that pins the release name, namespace and appVersion, as required by the testing conventions, and covers the enable/disable matrix, annotations, labels, TLS and a custom HTTP port. BREAKING CHANGE: The Ingress is no longer rendered when `service.http.enabled` is `false`. `ingress.className` now defaults to `nginx` instead of the cluster's default IngressClass. The undocumented `namespace` value no longer applies to the Ingress. Co-authored-by: Copilot <copilot@github.com>	2026-09-13 20:20:00 +02:00
volker.raschekandCopilot	41dcb48564	refactor(ingress): extract annotation, label and name rendering into helpers ... The Ingress was the last chart-managed resource that built its metadata inline. Annotations were rendered with a `range` over the values map, which indents each entry manually and cannot be reused, and the resource had no way to attach additional labels. Annotations, labels and the name are now rendered by helpers in `_ingresses.tpl`, matching the pattern already used by the other resources. This also adds `ingress.labels` so extra labels can be attached to the Ingress, and reorders the `ingress` keys in `values.yaml` to the convention of `enabled`, `annotations` and `labels` first. The `$httpPort` variable was assigned before the `range` over `ingress.hosts` and therefore resolved against the wrong context once the loop rebound the dot. It has been replaced by `$.Values.service.http.port`, which reads the value from the root context at the point of use. Co-authored-by: Copilot <copilot@github.com>	2026-09-13 19:34:56 +02:00