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 chart seems to suggest yes as it has a replicaCount setting, however the project also uses a levelDB which appears to be stored in a local file. Can that cause any issues, for example if a client obtains a token from instance A but then later uses that refresh token on instance B?
As this application will need to be up for any clients that have not yet logged in to pull or push anything deploying it twice seems necessary to prevent short outages.
The text was updated successfully, but these errors were encountered:
The chart seems to suggest yes as it has a replicaCount setting, however the project also uses a levelDB which appears to be stored in a local file. Can that cause any issues, for example if a client obtains a token from instance A but then later uses that refresh token on instance B?
As this application will need to be up for any clients that have not yet logged in to pull or push anything deploying it twice seems necessary to prevent short outages.
The text was updated successfully, but these errors were encountered: