Skip to content

feat(ingress): add ingressClassName support#50

Merged
xet7 merged 1 commit intowekan:mainfrom
Rohmilchkaese:fix/add-ingressClassName-support
Feb 19, 2026
Merged

feat(ingress): add ingressClassName support#50
xet7 merged 1 commit intowekan:mainfrom
Rohmilchkaese:fix/add-ingressClassName-support

Conversation

@Rohmilchkaese
Copy link
Contributor

@Rohmilchkaese Rohmilchkaese commented Feb 17, 2026

Summary

  • Add ingress.className value to set spec.ingressClassName on the Ingress resource
  • Remove deprecated kubernetes.io/ingress.class annotation from default values comment

The kubernetes.io/ingress.class annotation has been officially deprecated since Kubernetes 1.18 in favor of spec.ingressClassName (part of networking.k8s.io/v1). The chart currently has no way to set ingressClassName, forcing users to rely on the deprecated annotation.

Note: The kubernetes.io/ingress.class annotation is deprecated and may be removed in a future Kubernetes version. Users should migrate to ingress.className instead.

This change is fully backward compatible — when className is empty (the default), no ingressClassName field is rendered. Existing users relying on the annotation are not affected.

Test plan

  • helm template with className: "traefik"ingressClassName: traefik rendered in spec
  • helm template with className: "nginx"ingressClassName: nginx rendered in spec
  • helm template with className: "" (default) → no ingressClassName field (backward compatible)

The deprecated annotation kubernetes.io/ingress.class has been removed
from the default values. Users can now set ingress.className to specify
the ingress class via the spec.ingressClassName field, which is the
standard approach since networking.k8s.io/v1.
@xet7 xet7 merged commit 2d8d164 into wekan:main Feb 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants