When running clowder in multiple instances and using oath, the authentication piece needs to use a consistent clowder instance. The token used in the oauth flow is kept in memory.
The idea right now is for the ingress route to always pick a single instance for the login flow. Clowder right now runs as a deployment, which makes it harder to force the ingress route to always pick a single entity. Switching to a stateful set will allow us to add specific ingress routes for the login to always connect to a single instance.
When running clowder in multiple instances and using oath, the authentication piece needs to use a consistent clowder instance. The token used in the oauth flow is kept in memory.
The idea right now is for the ingress route to always pick a single instance for the login flow. Clowder right now runs as a deployment, which makes it harder to force the ingress route to always pick a single entity. Switching to a stateful set will allow us to add specific ingress routes for the login to always connect to a single instance.