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
While I generally agree that this is right, it is a breaking change that moves coredns from Guaranteed QoS to Best Effort which might have negative affects on deployments
Due to a bug in Helm there's no way for us to unset limits when using CoreDNS as sub chart.
helm/helm#12637
May I suggest we do this on the current values.yaml?
With the current chart there's no way for us deploy CoreDNS without CPU limits
Happy to open a PR
The text was updated successfully, but these errors were encountered: