Skip to content

Authentik outpost ingressClass not applied properly when using with Ingress-Nginx #16331

@Bykow

Description

@Bykow

Describe the bug

  • When creating an outpost with a specific ingressClass, no ingress gets created with that ingressClass
  • When updating the ingressClass of an outpost (i.e. from none to any ingressClass), the ingress doesn't change

To Reproduce
Steps to reproduce the behavior:

  1. Create an outpost for proxy type

  2. Set a valid ingressClass in Advanced settings -> kubernetes_ingress_class_name

  3. No ingress is created

  4. Create an outpost for proxy type

  5. Do not set any advanced settings

  6. Ingress is created with ingressClass

  7. Edit the outpost with an ingressClass in Advanced settings -> kubernetes_ingress_class_name

  8. The existing ingress is not edited

Expected behavior
Editing this value should update the ingress

Logs
Log of outpost pod

{"event":"Loaded config","level":"debug","path":"inbuilt-default","timestamp":"2025-08-22T07:43:16Z"}
{"event":"Loaded config from environment","level":"debug","timestamp":"2025-08-22T07:43:16Z"}
{"event":"Successfully connected websocket","level":"info","logger":"authentik.outpost.events","outpost":"9ec03361-c10f-46cb-b611-328fc36bc7af","timestamp":"2025-08-22T07:43:16Z"}
{"event":"Scheduling session cleanup job","level":"info","logger":"authentik.outpost.proxyv2.filesystemstore","timestamp":"2025-08-22T07:43:17Z"}
{"event":"Starting Metrics server","level":"info","listen":"0.0.0.0:9300","logger":"authentik.outpost.metrics","timestamp":"2025-08-22T07:43:17Z"}
{"event":"Starting HTTPS server","level":"info","listen":"0.0.0.0:9443","logger":"authentik.outpost.proxyv2","timestamp":"2025-08-22T07:43:17Z"}
{"event":"Starting HTTP server","level":"info","listen":"0.0.0.0:9000","logger":"authentik.outpost.proxyv2","timestamp":"2025-08-22T07:43:17Z"}
{"event":"Starting authentik outpost","hash":"tagged","level":"info","logger":"authentik.outpost","timestamp":"2025-08-22T07:43:17Z","version":"2025.8.0"}
{"event":"Starting session cleanup","level":"info","logger":"authentik.outpost.proxyv2.filesystemstore","timestamp":"2025-08-22T07:48:17Z"}

Version and Deployment (please complete the following information):

  • authentik version: 2025.08.0
  • Deployment: helm

Additional context
I have multiple ingressclasses in my cluster, not being able to assign an outpost per ingressclass is a showstopper for me.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions