-
Notifications
You must be signed in to change notification settings - Fork 53
Description
Hi, im migrating my docker-compose authentik into my new kubernetes cluster,
along the way I lost all a images/icons because they are now stored in rook ceph s3 and I couldnt find a way to migrate the volume mount from ./media into s3 yet.
But my biggest porting-over problem at the moment is that the ldap and radius outpots were previously written in my docker-compose file so they always ran the same version tag as the server and worker.
Now with the helm chart first of all there seems to be no way to enable radius or ldap again and if I deploy them manually their tags will drift away from the version used by the helm chart.
What is the recommended way to deploy ldap and radius as well with this helm chart and without writing a bunch of scripts to extract the recommended image and tag from the helm chart into custom deployments?
I tried playing around with extraDeployments: but it doesnt seem to work yet and I dont understand enough about kubernetes yet to debug this on my own:
extraDeploy:
- |
apiVersion: apps/v1
kind: Deployment
metadata:
name: authentik-ldap
namespace: authentik
spec:
replicas: 1
selector:
matchLabels:
app: authentik-ldap
template:
metadata:
labels:
app: authentik-ldap
spec:
containers:
- name: ldap
image: ghcr.io/goauthentik/outpost-ldap:{{ .Values.image.tag }}
env:
- name: AUTHENTIK_HOST
value: "https://authentik.example.com"
- name: AUTHENTIK_TOKEN
valueFrom:
secretKeyRef:
name: authentik-outpost-ldap
key: token
ports:
- containerPort: 3389
name: ldap