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

Update docs to reflect resource requests of pods #4472

Merged
merged 1 commit into from
Jan 14, 2022

Conversation

lbernick
Copy link
Member

Changes

Tekton previously modified step resource requests to request one large container (with the max resource request of any Step)
and resource requests of 0 in all other containers. This behavior was modified in v0.28.0 (#4176). Now, the Step resource requests are preserved
(unless any LimitRanges are present). This commit updates the documentation to reflect this change.

This commit also updates the description of how init container and container resource requests are combined to determine the resulting pod's
resource requests, based on Kubernetes documentation.

/kind documentation

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Docs included if any changes are user facing
  • Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Release notes block below has been filled in or deleted (only if no user facing changes)

Release Notes

NONE

Tekton previously modified step resource requests to request one large container (with the max resource request of any Step)
and resource requests of 0 in all other containers. This behavior was modified in v0.28.0. Now, the Step resource requests are preserved
(unless any LimitRanges are present). This commit updates the documentation to reflect this change.

This commit also updates the description of how init container and container resource requests are combined to determine the resulting pod's
resource requests, based on [Kubernetes documentation](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/#resources).
@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. kind/documentation Categorizes issue or PR as related to documentation. labels Jan 12, 2022
@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Jan 12, 2022
@lbernick
Copy link
Member Author

/assign @vdemeester

@lbernick
Copy link
Member Author

/test pull-tekton-pipeline-integration-tests

Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/meow

@tekton-robot
Copy link
Collaborator

@vdemeester: cat image

In response to this:

/meow

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 14, 2022
@ghost
Copy link

ghost commented Jan 14, 2022

Nice, thank you!

/lgtm

@tekton-robot tekton-robot assigned ghost Jan 14, 2022
@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 14, 2022
@lbernick
Copy link
Member Author

/test pull-tekton-pipeline-integration-tests

@tekton-robot tekton-robot merged commit 8c87bf9 into tektoncd:main Jan 14, 2022
@lbernick lbernick deleted the resources-docs branch January 24, 2022 15:28
@jerop jerop linked an issue Jan 24, 2022 that may be closed by this pull request
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Mar 17, 2022
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Mar 17, 2022
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Mar 17, 2022
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Mar 17, 2022
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Mar 17, 2022
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Mar 17, 2022
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Mar 17, 2022
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Mar 17, 2022
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Mar 17, 2022
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Mar 17, 2022
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Mar 17, 2022
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Mar 17, 2022
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Mar 17, 2022
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Mar 17, 2022
joshuasimon-taulia added a commit to joshuasimon-taulia/jx3-pipeline-catalog that referenced this pull request Oct 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

resource hoarding for steps of a taskrun
3 participants