-
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
Release v1 versions of Task, TaskRun, Pipeline, and PipelineRun CRDs #5541
Comments
@tektoncd/core-maintainers since remote resolution beta is in our 0.41.0 milestone, I think we should start work on this rather than blocking on the remaining work that needs to be done for custom tasks beta. It would be nice to release them all at once, but I don't see any reason why these CRDs in v1 wouldn't work with v1alpha1 Runs for the time being. Thoughts? |
Discussed in today's api wg: folks seem to be OK with going forward with this plan without blocking on custom tasks beta but would like to block on remote resolution beta. We should review our plan for supporting deprecated fields (#4546) before swapping our stored versions over to v1. |
Would like to confirm the understanding on the part iii. Basically what is needed here is changing most |
Yes, that sounds right to me! |
Deprecated features that needs to be handled as part of the storage version migration:
The followings are not blockers of the v1 storage swap:
|
What needs to be done before swapping v1 storage:
|
If that makes sense, my understanding is instead of addressing issues like #5964 , the round-trip conversion test is to prevent such issue from happening. Yes, I agree. But I think #5979 is going to be handled within the same PR of the storage swap since I could not figure out a way to separately isolate the TaskObject interface. |
Would you mind updating #5979 with the details of what you tried? |
Thanks to the guidance and talked offline with @vdemeester , the following would also be blockers/ bugs for v1 storage version change:
|
Aligned in WG @4 April that we are going to delay to v0.48, which is after the earliest LTS v0.47 to minimize impacts on LTS users while we are going to merge v1 storage swap soon as possible in early v0.48 to get enough window for fixing for v0.48. |
This commit makes the conversions required for reconciling the deprecated v1beta1 CustomTask public in the apis. part of tektoncd#5541
This commit makes the conversions required for reconciling the deprecated v1beta1 CustomTask exported in the apis. part of tektoncd#5541
Current blockers/ questions: |
This commit exports the conversions required for reconciling the deprecated v1beta1 CustomRun in the apis. part of tektoncd#5541
This is to update the current blockers:
|
|
@lbernick and I did some investigating around the test failures summarized in #6608 (tl;dr unit tests pass, some integration tests fail due to the issue in #6592) TODOs
|
Pipelines WG - this is at risk, blocked by an issue #6616 |
Seems like it's less possible to include this in v0.48. Should we move it to next release? |
cc @jerop |
This issue tracks the release of v1 api versions for Task, TaskRun, Pipeline, and PipelineRun.
Before doing this, we would like to wait for remote resolution beta (#4710), since we want to provide an alternative to taskref.bundle and pipelineref.bundle.
It would be nice to wait for custom tasks beta (#4313) so we can release v1 versions of these CRDs along with custom task beta, but there's still more work to do there and I'm not sure this should be a blocker.
Steps:
The text was updated successfully, but these errors were encountered: