Skip to content

Maybe change behaviour of admin user creation on updating

Currently the admin user is created on every deployment / upgrade of the scripts. We have to decide if we want that and if we want to reset the password every time:

Kubernetes API contains password/user of admin user, we can treat this in a few different ways:

  • We only use it during first installation
  • We only recreate the user during update if its missing. If it already exists, do not touch
  • Every run/update we create the user and set the password to the kubernetes defined string [current situation]
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information