-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't run Task including multiple steps with different resources requests/limits values #1933
Comments
This issue comes from where container requests are handled for a TaskRun, which is Basically, what is happening is that the last container or step for a TaskRun is set to the maximum values for
Since step 3 receives a request that is higher than its limit ( Because the max value is placed in the last container without thinking about the limit, it exceeds the limit. It seems like the implementation doesn't honor limits of the last step. |
/kind bug |
Prior to #1655, it looks like the last step index wasn't used to hold the max request. It looks like what was being done was finding the index of the highest resource request for memory, cpu, and ephemeral storage. So, instead of throwing everything as a single request in to the last container, it was leaving the max resource request in the index where it originally was while zeroing out anything that is not the max. This would make sense as then it would honor its limit. So my thought here is that the function should find the index and max value of memory, cpu, and ephemeral storage and leave those values where they are and zero out everything else. There is still the issue of #1045, but that I can handle separately as the container requests should factor in the minimum for the limit range for containers. |
/assign |
Expected Behavior
A
Task
can have multiplesteps
with different resources requests/limits values, where the n-1step
gets higher values than the latest step.Actual Behavior
While it works with Tekton Pipelines 0.8.0 and 0.9.2, since the 0.10.0 it is not possible to deploy a
Task
which defines astep
2 with higher values than the latest step.An error message like below is thrown (in that case the
spec.containers[2].resources.limit
value is512Mi
but thespec.containers[3].resources.limit
is128Mi
)Steps to Reproduce the Problem
The following
TaskRun
is used to reproduce the problem:Additional Info
it might be related to this update #1655 but I'm not sure.
The text was updated successfully, but these errors were encountered: