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
The operator will always apply a memory request of 200Mi to the Alertmanager pod, even if limits are already set. This is problematic if the limit is lower than the request, or if the user does not want an explicit request. I usually only set limits, as the Kubernetes API will automatically set the requests to match those limits and the QOS class will then be considered "Guaranteed". However, the QOS class is considered "Burstable" because of the default memory request. This should just be removed.
The operator will always apply a memory request of
200Mi
to the Alertmanager pod, even if limits are already set. This is problematic if the limit is lower than the request, or if the user does not want an explicit request. I usually only set limits, as the Kubernetes API will automatically set the requests to match those limits and the QOS class will then be considered "Guaranteed". However, the QOS class is considered "Burstable" because of the default memory request. This should just be removed.operator/controllers/factory/alertmanager.go
Lines 124 to 126 in aff55e6
The text was updated successfully, but these errors were encountered: