-
Notifications
You must be signed in to change notification settings - Fork 74
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
Add Support for Tekton Pipeline v1 APIs #352
Conversation
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.
/kind feature
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.
/hold
So I think This PR would make |
2480316
to
e71de6b
Compare
Per WG discussion - we are going to hold this PR until v0.5.0 is released, then we can cut over to v1. See #303 (comment) |
Keeping the hold on this PR - the logs feature is likely blocked by tektoncd/cli#1837 |
A new version of cli with v1 has been released. I would rebase and update with cli. |
31b2f5a
to
f91c812
Compare
Add support for storing objects in v1 CR.
/hold cancel |
@alan-ghelardi @dibyom @adambkaplan @sayan-biswas @enarha We should try to get this merge asap. |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester 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 |
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.
Most of the code upgrades look good.
I do have a few questions regarding upgrade scenarios:
- Can the apiserver handle updates from v1beta1 and v1 objects (ex - rolling upgrade of watchers)
- Do we record the object version in the underlying record? Will clients be able to decode v1beta1 and v1 objects?
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.
This file should not be added. Please remove and add a .gitignore entry.
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 looks like we have a few obsolete dependencies as well. Maybe we take this up in separate pull requests?
@@ -68,7 +68,7 @@ type ui struct { | |||
} | |||
|
|||
func main() { | |||
conn, err := grpc.Dial("localhost:8080", grpc.WithInsecure(), grpc.WithBlock()) | |||
conn, err := grpc.Dial("localhost:50051", grpc.WithInsecure(), grpc.WithBlock()) |
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.
Why change the port number?
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 think this was changed in a different pr. So will update this. It happened due to rebasing.
return json.Unmarshal(m.GetValue(), &v1beta1.TaskRun{}) | ||
return json.Unmarshal(m.GetValue(), &v1.TaskRun{}) |
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.
Will this break if the value data contains v1beta1.TaskRun
?
case "pipeline.tekton.dev/PipelineRun": | ||
return json.Unmarshal(m.GetValue(), &v1beta1.PipelineRun{}) | ||
return json.Unmarshal(m.GetValue(), &v1.PipelineRun{}) |
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.
Will this break if the value data contains v1beta1.PipelineRun
?
} else { | ||
// TODO(alan-ghelardi): remove this else once we support only | ||
// Tekton v1 API since the full embedded status will no longer | ||
// be supported. |
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.
+1 - great work @alan-ghelardi to mark this out ahead of time!
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.
Please remove this file. It was the source of a data race condition in our tests. We have replaced this "integration" controller test with a full end to end test.
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.
Changes to posgres-migrate are probably not necessary. This is a legacy tool from when this project used MySQL.
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.
Changes to postgres-migrate are probably not necessary.
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.
Changes to postgres-migrate are probably not necessary
/hold At the last working group meeting, @enarha wanted to take the lead on publishing a new release this week. We should wait on merging this change until that is complete. |
@khrm: 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. |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
Stale issues rot after 30d of inactivity. /lifecycle rotten Send feedback to tektoncd/plumbing. |
Rotten issues close after 30d of inactivity. /close Send feedback to tektoncd/plumbing. |
@tekton-robot: 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. |
We need to create an implementation based on WG call discussions and TEP in the community. |
No description provided.