Skip to content
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

Want to know the policy that Tekton request resource for the Task with multi containers #7148

Open
NEUerYZY opened this issue Sep 25, 2023 · 1 comment

Comments

@NEUerYZY
Copy link

I have done an experiment with the Tekton version v0.25.0 but meet a problem .

I try to make a TaskRun with the following description in a namespace with limit range 20C 20Gi.

spec:
  steps:
    - name: step1
      resources:
        requests:
          memory: 4Gi
          cpu: 2C
        limits:
          memory: 4Gi
          cpu: 2C
    - name: step2
      resources:
        requests:
          memory: 8Gi
          cpu: 4C
        limits:
          memory: 8Gi
          cpu: 4C
    - name: step3
      resources:
        requests:
          memory: 16Gi
          cpu: 8C
        limits:
          memory: 16Gi
          cpu: 8C

Then I found Tekton request the POD from K8S cluster with request resource 8C 16GI and limit resource 2+4+8 = 14C , 4+8+16=28Gi . The POD doesn't execute because of the namespace level limitation 20GI < limit resource 28Gi.

From the description of Pull request #723 and the document [https://github.com/tektoncd/pipeline/blob/v0.25.0/docs/tasks.md#defining-steps] . I can know that Tetkon reserve the max Request resource for multi containers rather than the sum of request . But there is no related description with Limit resource

So , all of above I want to know

  1. The principle that Tekton request limit resource from K8S cluster when a Task has multi containers .
  2. Is there any solution for this scene that can request the limit resource using the max limit resource among containers ?
@sibelius
Copy link

did you find the fix ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants