running >1 pod in a dynamic environment does not guarantee the service will be always available. while nothing in guaranteed, adding an optional podDisruptionBudget would allow users of the helm chart to avoid service outages due to voluntary pod eviction/planned maintenance (node replacement, etc).
Describe solutions and alternatives considered (optional)
take an optional podDisruptionBudget value (default to empty)
if defined, build a PodDisruptionBudgetk8s object for aws-privateca-issuer
Is there anything else you would like to add?
I'm happy to add this, but I'd like to ensure this is the direction the project wants to move before putting in the time.
Describe why this change is needed
running >1 pod in a dynamic environment does not guarantee the service will be always available. while nothing in guaranteed, adding an optional
podDisruptionBudget
would allow users of the helm chart to avoid service outages due to voluntary pod eviction/planned maintenance (node replacement, etc).Describe solutions and alternatives considered (optional)
podDisruptionBudget
value (default to empty)PodDisruptionBudget
k8s object for aws-privateca-issuerIs there anything else you would like to add?
I'm happy to add this, but I'd like to ensure this is the direction the project wants to move before putting in the time.