An introduction into integrating Authelia with Kubernetes.
The following areas are actively being worked on for Kubernetes:
- Detailed Documentation
- Helm Chart for Helm v3
- Kustomize Deployment
- Manifest Examples
Users are welcome to reach out directly by using any of our various contact options.
It’s strongly recommended that users setting up Authelia for the first time take a look at our Get Started guide. This takes you through various steps which are essential to bootstrapping Authelia.
The following section has special notes regarding utilizing Authelia with Kubernetes.
External Traffic Policy
Authelia (and all of your other applications) may receive an invalid remote IP if the service handling traffic to the
Kubernetes Ingress of your choice doesn’t have the
externalTrafficPolicy setting configured to
local as per the
Kubernetes preserving the client source ip documentation.
Enable Service Links
Authelia’s configuration management system conflicts with the
enableServiceLinks option when it’s set to
is the default. This should be changed to
false. See the
PodSpec v1 core documentation
for more details.
--- apiVersion: v1 kind: Pod metadata: name: authelia spec: enableServiceLinks: false ...
If using file-based authentication, the argon2id provider will by default use 1GB of RAM for password generation. This means you should allow for at least this amount in your deployment/daemonset spec and have this much available on your node, alternatively you can tweak the providers settings. Otherwise, your Authelia may OOM during login. See here for more info.