Considerations

• Downtime during any maintenance will increase as rolling updates/maintenance cannot be performed if going from a high available instance to single node instance.
• If you are configuring from high availability to single, note that there will be bit of downtime at the end of the configuration to restart the orchestrator to recognize the availability configuration has changed.
• When scaling from a single-node setup to a high-availability configuration, expect a brief connection interruption as the orchestrator restarts to integrate the newly added pod.
• Deployments which have a Disaster Recovery configured can not switch to single node without unconfiguring the diasaster recovery settings.

Configuring Availability in the UI

The High Availability panel is on the Adminstration tab of your deployment's console page.

You can choose the desired availability and click Save.