-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Add Support for managedBy field in TaskRun and PipelineRun #8965
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
base: main
Are you sure you want to change the base?
Conversation
/kind feature |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/hold cancel |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/assign @waveywaves @vdemeester |
/hold |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/retest |
@waveywaves Can you please review and merge this? |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/retest |
Added a "managedBy" field to delegate responsibility of controlling the lifecycle of PipelineRuns/TaskRuns. The semantics of the field: Whenever the value is set, and it does not point to the built-in controller, then we skip the reconciliation. * The field is immutable * The field is not defaulted Assisted By: Gemini
The following is the coverage report on the affected files.
|
/retest |
3 similar comments
/retest |
/retest |
/retest |
/hold |
@khrm, as noted from other maintainers as well, I think there is a fair point to be made here, that there isn't enough information on why this feature is being implemented. I think internally in the Red Hat team, we are well aware of it, but we need to take the community into account here and make sure that the proper design spec and issue are linked to the PR. We are missing the "whys" on this change and and relevant work that is being done in other upstreams. We need to add this in the PR description as it is just a part of the process. cc @afrittoli |
@waveywaves We did discuss this in WG call. We have an issue regarding this here: #8891 |
@afrittoli could you take a look at this, needs another set of eyes |
Added a "managedBy" field to delegate responsibility of controlling the lifecycle of PipelineRuns/TaskRuns.
The semantics of the field:
Whenever the value is set, and it does not point to the built-in controller, then we skip the reconciliation.
Addresses: #8891
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