-
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
[TEP-0135] Validate multiple PVC-based Workspaces in TaskRuns #6984
[TEP-0135] Validate multiple PVC-based Workspaces in TaskRuns #6984
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Prior to this commit, we only validate that 1 `PVC` is allowed to be binded to a `TaskRun` in `AffinityAssistantPerWorkspace` coschedule mode. The validation was skipped when there is no affinity assistant presents in the `TaskRun` (i.e. in standalone `TaskRun` or in `AffinityAssistantDisabled` coschedule mode). This commit adds the missing validation. This commit also updates workspace related documentation. /kind bug
8f2e7bd
to
f863aaf
Compare
/test pull-tekton-pipeline-beta-integration-tests due to timeout |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previously, with affinity assistant disabled, we let taskrun pods get scheduled by the kube scheduler, and they could non deterministically fail if a taskrun was bound to multiple pvcs, depending on how the pods ended up being scheduled. It sounds like this commit is preventing this from happening at all by rejecting these taskruns when the affinity assistant is disabled? Is this what you intended? I think a validation failure may be the better choice here, although this isn't backwards compatible; curious what others think
Yeah, you are right. I think ideally the validation should fail a standalone And I missed that prior to TEP-0135, we do allow standalone I would suggest that we do not merge this PR for now and leave it open to discussion. I will create a separate one just to adding documentation. WDYT? |
/hold |
SGTM! |
@QuanZhang-William: PR needs rebase. 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. |
@QuanZhang-William are you still working on this? (cleaning up old pull requests) |
@jerop. Thanks for the reminder. This PR introduces backward incompatible changes; and we don't have user request to add validation for >1 PVCs binded to a TaskRun. We can close this PR for now. /close |
@QuanZhang-William: Closed this PR. In response to this:
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. |
Prior to this commit, we only validate that 1
PVC
is allowed to be binded to aTaskRun
inAffinityAssistantPerWorkspace
coschedule mode. The validation was skipped when there is no affinity assistant presents in theTaskRun
(i.e. in standaloneTaskRun
or inAffinityAssistantDisabled
coschedule mode). This commit adds the missing validation.This commit also updates workspace related documentation.
/kind bug
Changes
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes