Global Taints, Tolerations, Affinity, and Anti-affinity Settings for Kubewarden Stack

[ksathe893]

Is your feature request related to a problem?

Yes, currently, it is not possible to configure global taints, tolerations, affinity, and anti-affinity settings for all components within the Kubewarden stack using the kubewarden helmchart. This makes it challenging to apply consistent scheduling constraints across the entire stack.the Kubewarden helmchart does not allow you to configure global taints, tolerations, affinity, and anti-affinity settings for all components within the Kubewarden stack

Solution you'd like

I would like to propose adding support for configuring global taints, tolerations, affinity, and anti-affinity settings in the Kubewarden stack (helmchart - values.yaml). This would enable administrators to define these settings once for the entire stack, rather than having to specify them individually for each component. This feature would enhance flexibility and simplify management of Kubewarden deployments in Kubernetes clusters.

Alternatives you've considered

• Editing the helm chart (per component) with the required settings.
• Patching the deployment for each component with required settings.

Anything else?

No response

[flavio]

Not yet in a workable state, I want to figure out if there are some common patterns about how to manage that inside of helm charts

[flavio]

I've asked/looked around. We could do something like Bitnami does:

In Bitnami they standardized it with podAffinityPreset and podAntiAffinityPreset to simplify the configurations to the end user, leaving the "advanced" configuration with the options affinity.podAffinity, affinity.nodeAffinity and tolerations. Those options are supported for all Bitnami charts, because they invested the time into standardizing it.

You can see this here for example

[flavio]

To whoever takes this card, please make a concrete example about how the helm chart is going to be changed before starting to work on that.