Kubernetes

UNDER CONSTRUCTION#

The following areas are actively being worked on for Kubernetes:

1. Detailed Documentation
2. Helm Chart for Helm v3
3. Kustomize Deployment
4. Manifest Examples

Users are welcome to reach out directly by using any of our various contact options.

Get started#

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.

Important Notes#

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 true which is the default. This should be changed to false. See the PodSpec v1 core documentation for more details.

Pod Example#

apiVersion: v1 kind: Pod metadata: name: authelia spec: enableServiceLinks: false …

## Frequently Asked Questions

### RAM usage

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](../../configuration/first-factor/file.md#memory). Otherwise,
your Authelia may OOM during login. See [here](https://github.com/authelia/authelia/issues/1234#issuecomment-663910799)
for more info.

[preserving the client source ip]: https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#preserving-the-client-source-ip