You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently trying the projects out, and I've an issue about authentik worker pods not running. After a little bit of debugging it seems that the cause is service account used by the worker deployment being "not created"
captain@glados:~$ kubectl describe rs/auth-authentik-worker-796d85c7dc -n infra
Name: auth-authentik-worker-796d85c7dc
# ...
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedCreate 14m (x19 over 35m) replicaset-controller Error creating: pods "auth-authentik-worker-796d85c7dc-" is forbidden: error looking up service account infra/auth-authentik: serviceaccount "auth-authentik" not found
And sure enough the service account seems to not have the assumed value
captain@glados:~$ kubectl get sa -n infra
NAME SECRETS AGE
auth 0 41m
auth-redis 0 41m
default 0 5d3h
# Exhaustive list
I don't really know charts templating system, so CMIIW: it seems that
which in this case happens to be auth, causing the mismatch between the resources values
To Reproduce
Steps to reproduce the behavior:
I didn't exactly note down precisely the steps, since this is happening on currently-running cluster, but IIRC it's just
helm upgrade --install auth -n infra goauthentik/ -f goauthentik.yaml
Where goauthentik/ is just the extracted charts from $ helm pull --untar --untardir goauthentik/ authentik/authentik --version 2023.5.4 and goauthentik.yaml is just the default value from the Installation docs page
Expected behavior
Service account should be created with the correct name (or the configuration value changed to follow the service account name).
Version and Deployment:
authentik version: 2023.5.4
Deployment: helm
The text was updated successfully, but these errors were encountered:
Describe the bug
Hello 馃憢
I'm currently trying the projects out, and I've an issue about authentik
worker
pods not running. After a little bit of debugging it seems that the cause is service account used by theworker
deployment being "not created"And sure enough the service account seems to not have the assumed value
I don't really know charts templating system, so CMIIW: it seems that
helm/charts/authentik-remote-cluster/templates/service-account.yaml
Line 5 in 69aef87
uses the
Release.Name
valuehelm/charts/authentik-remote-cluster/templates/_helpers.tpl
Lines 13 to 15 in 69aef87
which in this case happens to be
auth
, causing the mismatch between the resources valuesTo Reproduce
Steps to reproduce the behavior:
I didn't exactly note down precisely the steps, since this is happening on currently-running cluster, but IIRC it's just
Where
goauthentik/
is just the extracted charts from$ helm pull --untar --untardir goauthentik/ authentik/authentik --version 2023.5.4
andgoauthentik.yaml
is just the default value from the Installation docs pageExpected behavior
Service account should be created with the correct name (or the configuration value changed to follow the service account name).
Version and Deployment:
The text was updated successfully, but these errors were encountered: