FR: PodDisruptionBudget and Replicas

Open hazcod opened this issue 4 years ago • 1 comments

Summary

The current helm chart only allows for a single instance of the connect and operator to be deployed. This provides a higher risk in terms of availability.

Proposed solution

Add a replicas argument to values.yml with a default value of 1. Also add a PodDisruptionBudget with a max of 1..

Is there a workaround to accomplish this today?

No.

Mar 08 '22 08:03 hazcod

Thanks for the suggestion, I encourage you to go ahead and make a PR with this change and we can review to make sure all is well.

May 26 '23 17:05 jillianwilson