Skip to content
UMKIMDocs
Search limited to 0.1.0. Switch to the latest version for up-to-date results.

Ingress auth

This content is for 0.1.0. Switch to the latest version for up-to-date documentation.

Ingress authentication can add an optional forward-auth layer to selected edge routes. It is separate from console authentication and remains experimental in v0.1.0.

Configure the feature only through reviewed inventory, encrypted vault values, and authenticated console workflows. Use separate per-cluster credentials when needed; never include passwords, session material, or API bearer values in documentation, commands, or source control.

Before exposing a route, independently validate its DNS, TLS, network, authorization, session, and recovery behavior. This release does not provide a supported public access-control or certificate-management guarantee.

See fleet-edge and Secrets and vault.