helm
helm copied to clipboard
Websockets dont work with default configuraton
the authentik admin ui keeps complaining that websocket connections are failing - this was not an issue before I migrated to kubernetes (was using docker+nginx reverse proxy). I did migrate everything, including the database, so unsure if theres a hidden option in the database or whether websockets in the ingress created by the helm are dodgy
with the following values:
values:
global:
volumes:
- name: media
persistentVolumeClaim:
claimName: authentik-media-pvc
- name: custom-css
configMap:
name: authentik-custom-css
volumeMounts:
- name: media
mountPath: /media
- name: custom-css
mountPath: /web/dist/custom.css
subPath: custom.css
authentik:
secret_key: xxx
postgresql:
password: xxx
email:
host: mailxxx
port: "587"
username: no-reply@xxx
password: xxx
use_tls: true
timeout: "30"
from: no-reply@xxx
server:
ingress:
enabled: true
ingressClassName: external-nginx
hosts:
- auth.xxx
tls:
- secretName: wildcard.xxx
hosts:
- auth.xxx
podAnnotations:
backup.velero.io/backup-volumes: media
postgresql:
enabled: true
auth:
password: xxx
primary:
persistence:
size: 256Mi
podAnnotations:
backup.velero.io/backup-volumes: data
redis:
enabled: true
master:
persistence:
size: 128Mi