direct upgrade not possible, need to undeploy before #6

Open
opened 2023-12-21 18:56:45 +00:00 by iexos · 1 comment
Member

its not possible to directly upgrade authentik, as worker and server must use the same image. one of them won't be shut down before the other new one comes up, which it won't as it will fail to start with the other old one still running

Not sure if its possible to fix within the recipe or even abra though

its not possible to directly upgrade authentik, as worker and server must use the same image. one of them won't be shut down before the other new one comes up, which it won't as it will fail to start with the other old one still running Not sure if its possible to fix within the recipe or even abra though
Owner

I would then just release a major recipe version and a release note saying this is the only way. More in the docs. So when people run upgrade they get this note saying "STOP!" and undeploy/deploy etc. safely. That seems to generally work so far.

I would then just release a major recipe version and a release note saying this is the only way. More in the docs. So when people run `upgrade` they get this note saying "STOP!" and `undeploy`/`deploy` etc. safely. That seems to generally work so far.
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/authentik#6
No description provided.