-
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-0114: Added CustomRun references and specifications to v1beta1 #5403
Conversation
Hi @vsinghai. Thanks for your PR. I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
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.
|
22d3640
to
e1c0422
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
Below are some problems and resolutions I encountered while creating this PR: Problems:
Resolutions:
|
In v1alpha1, `Runs` have `Pod` templates. However, `Runs` do not always create `Pods`. In this change, we propose that `Runs` in v1beta1 should not have `Pod` templates - specific `Custom Tasks` implementation can support that in their own specifications. Context: tektoncd/pipeline#5403 (comment) Many thanks to @lbernick for catching this issue!
/assign |
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.
As review goes, I can see this is such a large and important effort for Custom Task Beta. Appreciate your work here!
}, | ||
"metadata": { | ||
"default": {}, | ||
"$ref": "#/definitions/v1beta1.PipelineTaskMetadata" |
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.
I'm not sure if this is correct? Why is it PipelineTaskMetadata? 🤔
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.
it is correct, Metadata PipelineTaskMetadata json:"metadata,omitempty"
, found in customrun_types.go
line 39. The swagger.json
files are autogenerated files.
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.
@jerop same here
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.
@XinruZhang this is also another case of reusing the metadata type -- we can rename it to something more appropriate for all places that it's used but would rather leave it out of scope for this change
Thank you @XinruZhang for the feedback! :) |
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.
|
Prior to this commit, we proposed migrating `Custom Tasks` and `Runs` to beta. Today, [embedded specs](https://github.com/tektoncd/pipeline/blob/main/docs/runs.md#2-specifying-the-target-custom-task-by-embedding-its-spec) are in `Run.Spec.Spec`. In this commit, we will align the embedded specs with the rest of the API such that it's `CustomRun.Spec.CustomSpec`. Fixes issue [tektoncd#5154](tektoncd#5154) /cc @jerop /cc @dibyom /kind feature
The following is the coverage report on the affected files.
|
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jerop, lbernick 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 |
In v1alpha1, `Runs` have `Pod` templates. However, `Runs` do not always create `Pods`. In this change, we propose that `Runs` in v1beta1 should not have `Pod` templates - specific `Custom Tasks` implementation can support that in their own specifications. Context: tektoncd/pipeline#5403 (comment) Many thanks to @lbernick for catching this issue!
Changes
Prior to this commit, we proposed migrating
Custom Tasks
andRuns
to beta. Today, embedded specsare in
Run.Spec.Spec
.In this commit, we will align the embedded specs
with the rest of the API such that it's
CustomRun.Spec.CustomSpec
.Fixes issue #5154
Fixes issue #5153
/cc @jerop
/cc @dibyom
/kind feature
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
[n/a] Has Docs included if any changes are user facing
functionality, content, code)
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep[n/a] Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
Release Notes