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
When pixelfed is deployed in a single pod, this is problematic since Horizon exits, but the rest of the pod continues to run (I think this is because of the CMD script of the container?)
When pixelfed is deployed with a separate worker pod, this is less problematic, but the pod will restart a few times.
Not sure of the best solution right now, but figured I'd document this.
The text was updated successfully, but these errors were encountered:
Hmmm, we can separate the deployments and put a liveness/readiness probe on the horizon deployment to retry x amount of times. Maybe have it try 10 times to be safe? I feel like as long as it eventually becomes healthy, that's ok?
Horizon requires Redis/Valkey being available to start properly. This can fail during initial deployment
When pixelfed is deployed in a single pod, this is problematic since Horizon exits, but the rest of the pod continues to run (I think this is because of the CMD script of the container?)
When pixelfed is deployed with a separate worker pod, this is less problematic, but the pod will restart a few times.
Not sure of the best solution right now, but figured I'd document this.
The text was updated successfully, but these errors were encountered: