3 Commits

Include renames

Author	SHA1	Message	Date
volker.raschekandCopilot	761921faed	test(ingress): align assertions with the release name and namespace ... The suite header was changed to the release `gitea-unittests` in the namespace `testing`, but the assertions still expected the previous `gitea-unittest` and `gitea-debug`. That made four cases fail on the rendered resource name, the `app.kubernetes.io/instance` label and the backend Service name. Renovate comments had additionally been copied into the expected `app.kubernetes.io/version` and `version` label values. They only matched by accident, because YAML strips the trailing comment from an unquoted scalar. Removing them keeps the assertions honest about what is actually compared. Co-authored-by: Copilot <copilot@github.com>	2026-09-14 15:24:55 +02:00
volker.raschek	c510e06609	fix(Makefile): update targets and add link checker	2026-09-13 22:51:05 +02:00
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