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 current controller logic for managing "request" resources when LimitRanges are present takes the "default" resource value and divides it by the number of containers in a Pod. This is close, but not quite correct as "sidecars" are run in parallel so should not be part of this calculation
skaegi
changed the title
Resource Memory and CPU Request Distribution does not handle sidecars correctly
LimitRange Memory and CPU Request Distribution does not handle sidecars correctly
Jun 15, 2022
Looking more carefully at https://github.com/tektoncd/pipeline/blob/main/pkg/internal/limitrange/transformer.go#L35 -- we're doing more than we need to here. We should only be transforming "Step" containers and should only be spreading "requests". For "limits" in Step containers as well as sidecars and the rest of the containers we should just let LimitRanger do its magic.
The current controller logic for managing "request" resources when LimitRanges are present takes the "default" resource value and divides it by the number of containers in a Pod. This is close, but not quite correct as "sidecars" are run in parallel so should not be part of this calculation
For...
Expected Behavior
Actual Behavior
The text was updated successfully, but these errors were encountered: