You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
By default, Applications -> Outposts -> Authentik Embedded Outpost -> Advanced Settings -> Configuration -> kubernetes_ingress_class_name is set to null. Changing this to any other value has no effect on the actual kubernetes ingress class.
To Reproduce
Steps to reproduce the behavior:
Run 'kubectl get ingress ak-outpost-authentik-embedded-outpost' and note the CLASS (it's null by default).
Navigate to Applications -> Outposts -> Authentik Embedded Outpost -> Advanced Settings -> Configuration -> kubernetes_ingress_class_name - set this to 'nginx' and select 'Update'
Run 'kubectl get ingress ak-outpost-authentik-embedded-outpost'. CLASS is still null.
Expected behavior
The embedded outpost should reflect the configured kubernetes ingress class name.
Version and Deployment (please complete the following information):
2025.2.4
authentik version: 2024.4.0 (and earlier)
Deployment: helm w/ kubernetes nginx ingress
Additional context
Issue has been observed consistently across multiple Authentik instances. Rollout/restart of the server/worker deployments has no effect. If an ingress class is explicitly set by proxied applications, the net result is a 404 error due to the ingress class mismatch.
The text was updated successfully, but these errors were encountered:
Describe the bug
By default, Applications -> Outposts -> Authentik Embedded Outpost -> Advanced Settings -> Configuration -> kubernetes_ingress_class_name is set to null. Changing this to any other value has no effect on the actual kubernetes ingress class.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The embedded outpost should reflect the configured kubernetes ingress class name.
Version and Deployment (please complete the following information):
2025.2.4
Additional context
Issue has been observed consistently across multiple Authentik instances. Rollout/restart of the server/worker deployments has no effect. If an ingress class is explicitly set by proxied applications, the net result is a 404 error due to the ingress class mismatch.
The text was updated successfully, but these errors were encountered: