You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Usually Helm charts don't set resource constraints by default, so that chart users may size the applications up to fit specific deployments. The preferred QoS class is also highly dependent on each deployment.
Since this project is meant as a generic Helm chart for stateless applications following a specific set of criteria, I'd avoid setting constraints by default to make it as easy as can be for anybody to use the chart.
Great observation, @d3adb5! Our approach is to make this opinionated while incorporating essential best practices. We're considering establishing absolute minimum requests and limits within the Helm chart. But indeed this is debatable
https://github.com/stakater/application/blob/master/application/values.yaml#L213-L220
and set same limits
The text was updated successfully, but these errors were encountered: