#Server/Worker pods not deployed as expected

1 messages · Page 1 of 1 (latest)

orchid oriole
#

I've tested with the sample values.yaml provided in the installation instructions and with my customized values as outlined below:

authentik:
  image:
    repository: ghcr.io/goauthentik/server
    tag: 2023.6.1
    pullPolicy: Always
  authentik:
    secret_key: secretkeyhere
    nodeSelector: {}
    log_level: debug
    email:
      host: smtp.gmail.com
      port: 587
      use_ssl: false
      use_tls: true
      timeout: 30
    outposts:
      docker_image_base: ghcr.io/goauthentik/%(type)s:%(version)s
    error_reporting:
      enabled: true
    postgresql:
      user: authentik
      name: authentikdb
      password: password
      host: postgres-host
      port: 5432
    redis:
      host: redis-host
  ingress:
    enabled: true
    hosts:
      - host: auth.test.com
        paths:
          - path: "/"
            pathType: Prefix
postgresql:
  enabled: false
redis:
  enabled: false

From what I can observe it creates all of the resources except for the server/worker deployment/pods.

It's probably something glaringly simple my overworked brain is missing, any ideas here?

image.png
pulsar flame
#

you have a whole authentik: section which is not needed IIRC

orchid oriole
#

It’s the chart within a chart format, but I also have ran it with the default values from the chart repo as well to the same effect.

pulsar flame
#

do you mind showing the argocd app directly?

orchid oriole
#

Yea I can shortly, walked away from the pc. Thanks for looking at it.

pulsar flame
#

helm template authentik authentik/authentik -f /tmp/values.yml --version 2023.6.1 with the values you pasted without the nested authentik: section gives me deployments for the server and worker at replica 1

orchid oriole
#

It must be argo specific quirk then because I tested it against the following "example" values in the instructions and saw the same behavior:

authentik:
  secret_key: "VGQixuTWcxajHZPw5sedmFZdCWMBcijncopHih85mX53JY0x2Z"
  # This sends anonymous usage-data, stack traces on errors and
  # performance data to sentry.beryju.org, and is fully opt-in
  error_reporting:
    enabled: true
  postgresql:
    password: "testpassword0101"

ingress:
  enabled: false

postgresql:
  enabled: false
  postgresqlPassword: "testpassword0101"
redis:
  enabled: false
pulsar flame
#

that's really weird, we're using argo internally to deploy authentik and have not had any issue

orchid oriole
#

I'll check the argo logs to see if anything funky appearing there.

pulsar flame
#

let me dump you one of our authentik applications so you can see if anything seems off with yours

orchid oriole
#

I had it working a year or so ago but when we moved I tore down the cluster and never re-deployed it till now. Only thing I really changed was the app version.

pulsar flame
orchid oriole
#

Appreciate it, I'll see if I can get it sorted.

pulsar flame
#

yeah I don't see anything weird, although you're in 2022.9.0 so a bit might have changed since then

orchid oriole
#

Yea this looks like it's going to be a huge trip down the rabbit hole. Also that was just an example I have my Chart/values updated to latest from the authentik helm repo.

#

Looks like I was barking up the wrong tree, I nuked the Chart that I pulled from the authentik helm repo and recreated a more simplistic one with no extra dependencies. Not worth debugging further, but was enough to just define:

name: authentik
apiVersion: v2
version: 2023.6.1
dependencies:
  - name: authentik
    version: 2023.6.1
    repository: https://charts.goauthentik.io

instead of

apiVersion: v2
version: 2023.6.1
appVersion: 2023.6.0
name: authentik
description: authentik is an open-source Identity Provider focused on flexibility and versatility
type: application
home: https://goauthentik.io
sources:
  - https://goauthentik.io/docs/
  - https://github.com/goauthentik/authentik
keywords:
  - authentication
  - directory
  - identity
  - idp
  - ldap
  - oauth
  - oidc
  - proxy
  - saml
  - scim
  - single-sign-on
  - sp
  - sso
icon: https://goauthentik.io/img/icon.png
maintainers:
  - name: authentik Team
    email: [email protected]
    url: https://goauthentik.io
dependencies:
  - name: postgresql
    version: 10.16.2
    repository: https://charts.goauthentik.io
    condition: postgresql.enabled
  - name: redis
    version: 15.7.6
    repository: https://charts.goauthentik.io
    condition: redis.enabled
  - name: authentik-remote-cluster
    repository: https://charts.goauthentik.io
    version: 1.2.1
    condition: serviceAccount.create
    alias: serviceAccount
annotations:
  artifacthub.io/changes: |
    - kind: changed
      description: upgrade to authentik 2023.6.0
  artifacthub.io/license: GPL
  artifacthub.io/links: |
    - name: GitHub
      url: https://github.com/goauthentik/authentik
    - name: Docs
      url: https://goauthentik.io/docs/
  artifacthub.io/maintainers: |
    - name: authentik Team
      email: [email protected]
      url: https://goauthentik.io
  artifacthub.io/images: |
    - name: authentik
      image: ghcr.io/goauthentik/server:2023.6.0
      whitelisted: true
    - name: authentik-outpost-proxy
      image: ghcr.io/goauthentik/proxy:2023.6.0
      whitelisted: true
    - name: authentik-outpost-ldap
      image: ghcr.io/goauthentik/ldap:2023.6.0
      whitelisted: true
    - name: authentik-outpost-radius
      image: ghcr.io/goauthentik/radius:2023.6.0
      whitelisted: true
  artifacthub.io/screenshots: |
    - title: User interface
      url: https://goauthentik.io/img/screen_apps_light.jpg
    - title: Admin interface
      url: https://goauthentik.io/img/screen_admin_light.jpg

Actually looking back at that I wonder if the mismatch in app version {2023.6.1} in values vs {2023.6.0} in chart could have had anything to do with it.