-
Notifications
You must be signed in to change notification settings - Fork 600
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
[WIP]: Migrate channel reconciler to use messaging.* v1 resources #3789
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: nlopezgi The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
If anyone has any pointers to help here. I'm stuck in the migration for channel (this PR) and subscription with the same error.
This error only occurs for the test case that includes dealing with a v1alpha1 Channelable resource. I'm not even sure if this test case is relevant. I tried to make this test work by creating a v1.Channelable, however, this also fails as lots of the conditions are not met - seems the behavior for this test depends on it using a v1alpha1 Channelable. The underlying issue I have, I think, is that I'm not sure how to properly migrate testing/v1beta1/channelable.go. This file seems to create a v1alpha1 Channelable which depends on using v1beta1 resources ( |
wanna skip this testcase, @nlopezgi ? |
So I looked a bit more at the types code to try to understand what is happening. I think the core issue is related to the ChannelableCombined. This type is supposed to represent "a skeleton type wrapping Subscribable and Addressable of both v1alpha1 and v1beta1 duck types". This leads me to think that as part of the types migration we need to add something else there for the Subscribable and Addressable for v1, otherwise we might end up breaking in some form backward compatibility (but again, I know little of how these things evolve in practice, so I might be missing something) thoughts @matzew ? |
Yes, that's what I thought too. BTW, some chat around this: https://knative.slack.com/archives/C9JP909F0/p1595856750119700 |
Thanks for confirming. I'll prepare a PR adding that. |
@nlopezgi can you rebase your PR her e? |
Thanks, I'm working on the PR. I rebased locally but still running into some issues, hope to make some progress later today. |
This pull request introduces 4 alerts when merging 7bc321e into f132f49 - view on LGTM.com new alerts:
|
This pull request introduces 4 alerts when merging 506f7a9 into 951a8d0 - view on LGTM.com new alerts:
|
The following is the coverage report on the affected files.
|
This pull request introduces 4 alerts when merging 606e5a1 into 951a8d0 - view on LGTM.com new alerts:
|
This pull request introduces 4 alerts when merging 857e611 into e8b5057 - view on LGTM.com new alerts:
|
This pull request introduces 4 alerts when merging 8e80582 into e8b5057 - view on LGTM.com new alerts:
|
I've rebased and tried everything I can think of but I'm still seeing tests fail with the same error as before (#3789 (comment)).
|
@nlopezgi I didn't also figure out how to fix this problem.
Not sure if this is a valid test. |
@nlopezgi
But, I fixed the compile errors first. See the latest 2 commits here: https://github.com/knative/eventing/pull/3860/commits |
This pull request introduces 4 alerts when merging 8672643 into 9f3fb3f - view on LGTM.com new alerts:
|
@@ -80,9 +80,9 @@ type ChannelableCombinedStatus struct { | |||
// SubscribableTypeStatus is the v1alpha1 part of the Subscribers status | |||
SubscribableTypeStatus `json:",inline"` | |||
// SubscribableStatus is the v1beta1 part of the Subscribers status. | |||
eventingduckv1beta1.SubscribableStatus `json:",inline"` | |||
SubscribableStatusv1beta1 eventingduckv1beta1.SubscribableStatus `json:",inline"` |
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.
Just to make sure I understand. We should be dropping the duck/v1alpha1, since we're dropping the support for v1alpha1 API shapes as per:
https://knative.dev/community/contributing/mechanics/release-versioning-principles/
They were not served in the .16, so we should not be using them here. Are we just leaving the pkg in v1alpha1 as is to make the changes smaller? I guess what I'm asking is, I feel like we should be dropping the duck/v1alpha1/channelable* related things, because v1alpha1 API is no longer supported, so would make more sense to only have a v1beta1 and v1 only. Or, am I missing something (still catching up after vacation :) )
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.
that's good to hear. dropping v1alpha1 would make things easier.
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.
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.
awesome sauce, thanks much for doing this!
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.
one extra thing to keep in mind... if we drop v1alpha1 now, I think eventing-contrib won't be able to update-deps until we move natss out of there or we fix it..
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.
Issue to migrate NATSSChannel to v1 Channelable: knative/eventing-contrib#1485
Issue to move NATSSChannel to a separate repo: knative/eventing-contrib#1487
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.
#3871 is now ready for review. Not sure if it needs to be put on hold until all deps are also updated. Please put on hold if needed. Will be closing this one.
@nlopezgi: The following tests failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
The following jobs failed:
Failed non-flaky tests preventing automatic retry of pull-knative-eventing-integration-tests:
and 62 more. |
lets move it out.
asap
On Wed 19. Aug 2020 at 18:30, Ignacio (Nacho) Cano ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In pkg/apis/duck/v1alpha1/channelable_combined_types.go
<#3789 (comment)>:
> @@ -80,9 +80,9 @@ type ChannelableCombinedStatus struct {
// SubscribableTypeStatus is the v1alpha1 part of the Subscribers status
SubscribableTypeStatus `json:",inline"`
// SubscribableStatus is the v1beta1 part of the Subscribers status.
- eventingduckv1beta1.SubscribableStatus `json:",inline"`
+ SubscribableStatusv1beta1 eventingduckv1beta1.SubscribableStatus `json:",inline"`
one extra thing to keep in mind... if we drop v1alpha1 now, I think
eventing-contrib won't be able to update-deps until we move natss out of
there or we fix it..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3789 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABGPTSSGUANTZPJZ6HVBK3SBP4Z3ANCNFSM4PVZ64SA>
.
--
Sent from Gmail Mobile
|
Closing in favor of #3871. See comments above for more details. |
Part of #3584
Proposed Changes
fyi @matzew
This is a WIP PR as tests are currently failing and I have not been able to figure out how to fix them.