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
For availability reasons, it would be ideal to have more than one replica when running as a deployment. Right now replicas is hardcoded to one. If the node the pod is running on goes down, we loose this metric until the pod is rescheduled onto another node.
Is there a reason why this was not added from the start?
I'd be happy to put up a PR for the helm chart edits!
The text was updated successfully, but these errors were encountered:
For availability reasons, it would be ideal to have more than one replica when running as a deployment. Right now replicas is hardcoded to one. If the node the pod is running on goes down, we loose this metric until the pod is rescheduled onto another node.
Is there a reason why this was not added from the start?
I'd be happy to put up a PR for the helm chart edits!
The text was updated successfully, but these errors were encountered: