-
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
Switch the Default Value of Feature Flag custom-task-version
to v1beta1
#5961
Switch the Default Value of Feature Flag custom-task-version
to v1beta1
#5961
Conversation
844e52a
to
3da4193
Compare
3da4193
to
c56a687
Compare
c56a687
to
7876e0b
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
7876e0b
to
b1cff8d
Compare
The following is the coverage report on the affected files.
|
…beta1` Prior to this commit, the feagure flag `custom-task-version` is default to `v1alpha1`, PipelineRun reconciler will create `v1alpha1` Custom Task out of a PipelineTask defined in a Pipeline. To support the migration story for Custom Task (see [the migration doc](https://github.com/tektoncd/pipeline/blob/main/docs/migrating-v1alpha1.Run-to-v1beta1.CustomRun.md)), this commit switches the default value to `v1beta1` in release v0.44.0 in order to make PipelineRun reconciler create `v1beta1.CustomRun` by default.
b1cff8d
to
cdd0971
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abayer 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 |
One question, why this pr is labeled as cleanup? It seems a change |
Good question, this is labeled as a cleanup PR of Custom Task Beta promotion -- remaining works of Custom Task Beta promotion while the beta Custom Task is ready to use, I'm open to suggestions :) |
I think kind "misc" is most appropriate. I agree with Yongxuan that it's surprising for a "cleanup" PR to make functional changes. |
@XinruZhang: The label(s) 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. |
SG! /kind misc |
/lgtm |
Changes
Switch the Default Value of Feature Flag
custom-task-version
tov1beta1
Prior to this PR, the feagure flag
custom-task-version
is default tov1alpha1
, PipelineRun reconciler will createv1alpha1
Custom Task out of a PipelineTask defined in a Pipeline.To support the migration story for Custom Task (see the migration doc), this PR switches the default value to
v1beta1
in release v0.44.0 in order to make PipelineRun reconciler createv1beta1.CustomRun
by default./kind cleanup/kind misc
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