-
Notifications
You must be signed in to change notification settings - Fork 266
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
Update Eventing Sources API to v1 #1299
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.
@dsimansk: 0 warnings.
In response to this:
Description
Follow-up on recent
v1alpha1
removal from Eventing main.
knative/eventing#5318Changes
- Update to
APIServerSource, ContainerSource, PingSource & SinkBinding
API tosources/v1
/cc @knative/client-reviewers
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.
There's one open question though. PingSource was promoted to @rhuss @maximilien any objections to the above? I'm mainly asking due to implications for |
Yeah, let's stay with PingSource v1beta2. If Eventing goes to Knative 1.0 with v1beta2, too, I don't see any problems to use this for a 1.0 client. |
@lionelvillard Are there any plans for Evention 1.0 to remove PingSource v1beta2, too ? |
We have to keep v1beta2 for at least of couple of releases. |
/retest |
|
||
"knative.dev/client/pkg/util" | ||
) | ||
|
||
func TestSimpleCreatePingSource(t *testing.T) { | ||
mysvc := &servingv1.Service{ | ||
TypeMeta: v1.TypeMeta{Kind: "Service", APIVersion: "serving.knative.dev/v1"}, | ||
ObjectMeta: v1.ObjectMeta{Name: "mysvc", Namespace: "default"}, | ||
TypeMeta: metav1.TypeMeta{Kind: "Service", APIVersion: "serving.knative.dev/v1beta2"}, |
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.
Serving v1beta2 ?
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.
Looks good, however while cross checking it looks like that there has been a gotcha when reverting from v1 back to v1beta2 for the ping source (see comment inline). Not sure if other parts are affected, too.
/retest /lgtm |
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.
/ok-to-test
/lgtm
Looks like that the test indeed captured a valid issue:
i.e. there is no output of the connected sink. |
Well, this one was pretty hard to find actually. 😓 Update: adding more details. The above change/fix was backported to Eventing patch release |
The following is the coverage report on the affected files.
|
That's fine I would say, as we can always say that's an issue with the backend and the fix is, to update the eventing backend to 0.22.1 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhuss 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 |
Description
Follow-up on recent
v1alpha1
removal from Eventing main.knative/eventing#5318
Changes
APIServerSource, ContainerSource, PingSource & SinkBinding
API tosources/v1
/cc @knative/client-reviewers