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..
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 tovalues.yml
with a default value of1
. Also add aPodDisruptionBudget
with a max of1.
.Is there a workaround to accomplish this today?
No.