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
The LofiFocus service is down and is pending an ingress update!
It was on our older docker swarm and is being migrated over to our kubernetes / supabase structure.
We have a couple options on how we can resolve this in the future, but usually a deep change in infra has some downsides.
The current plan to handle this is forward the sub-domain to the new music app and merge the LofiFocus into a service for the music application.
I am still working out the kinks with the Kubernetes ingress system, we might end up having to place a new load balancer after the Nginx or setup another HA Proxy for the subdomain routing. The other idea was to have Traefik handle our subdomains again but that template is on the older Traefik, so it would have to be rewritten again regardless.
The text was updated successfully, but these errors were encountered:
The LofiFocus service is down and is pending an ingress update!
It was on our older docker swarm and is being migrated over to our kubernetes / supabase structure.
We have a couple options on how we can resolve this in the future, but usually a deep change in infra has some downsides.
The current plan to handle this is forward the sub-domain to the new music app and merge the LofiFocus into a service for the music application.
I am still working out the kinks with the Kubernetes ingress system, we might end up having to place a new load balancer after the Nginx or setup another HA Proxy for the subdomain routing. The other idea was to have Traefik handle our subdomains again but that template is on the older Traefik, so it would have to be rewritten again regardless.
The text was updated successfully, but these errors were encountered: