-
Notifications
You must be signed in to change notification settings - Fork 592
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
adding istion annotation (#3534) #3557
adding istion annotation (#3534) #3557
Conversation
Hi @vayyappaneni. Thanks for your PR. I'm waiting for a knative 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. |
/assign @markusthoemmes |
/ok-to-test |
/test pull-knative-eventing-upgrade-tests |
1 similar comment
/test pull-knative-eventing-upgrade-tests |
/test pull-knative-eventing-integration-tests |
/test pull-knative-eventing-upgrade-tests |
1 similar comment
/test pull-knative-eventing-upgrade-tests |
You might want to backport this one first: #3543. |
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
@googlebot I fixed it. |
@markusthoemmes @pierDipi @vaikas |
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
This is weird, cherry-picking @vaikas commit cause the CLA to go out of wack. We are gonna just manually make the fix to backport instead of cherry-picking. |
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.
Produced via:
gofmt -s -w $(find -path './vendor' -prune -o -path './third_party' -prune -o -name '*.pb.go' -prune -o -type f -name '*.go' -print)
goimports -w $(find -name '*.go' | grep -v vendor | grep -v third_party | grep -v .pb.go | grep -v wire_gen.go)
Co-authored-by: Matt Moore <mattmoor@vmware.com>
I guess I'm little confused what we're backporting here? Shouldn't it just be a rebase? I'm mosdef not a git expert, but something seems wrong here. |
lol, I see, you're porting them to .16.1 release :) LOL sorry about the noise... |
@vaikas do you know why the CLA got invalidated when we cherry-picked your commit? |
/retest |
/test pull-knative-eventing-upgrade-tests |
@AceHack no idea, in the past I've seen the emails go out of whack when things get cherrypicked, but no idea. |
Oh snap, looks like this needs to be cherrypicked also: The errors are exactly what we saw in the main branch. |
* try to dump some state * use client wait or fail * create broker directly
/retest |
@vaikas it seems cherry-picking your PR directly into 16 branch caused unit test issues. Can you offer any advice or do you know if there are other things we should cherry pick. |
/retest |
Looks like backporting it missed some bits? vs. test/upgrade/prober/configuration.go:22:2: imported and not used: "knative.dev/eventing/pkg/reconciler/sugar" |
The following jobs failed:
Failed non-flaky tests preventing automatic retry of pull-knative-eventing-upgrade-tests:
|
@markusthoemmes @vaikas It's finally working, thanks for all the help. Can we get it merged? Thanks again. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vaikas, vayyappaneni 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 |
* adding istion annotation (knative#3534) * backporting knative#3543 * Update test/lib/duck/resource_inspectors.go Co-authored-by: Matt Moore <mattmoor@vmware.com> * Use the standard resource creation libs for upgrade tests. (knative#3539) * try to dump some state * use client wait or fail * create broker directly * removed the unused import Co-authored-by: Matt Moore <mattmoor@vmware.com>
* adding istion annotation (knative#3534) * backporting knative#3543 * Update test/lib/duck/resource_inspectors.go Co-authored-by: Matt Moore <mattmoor@vmware.com> * Use the standard resource creation libs for upgrade tests. (knative#3539) * try to dump some state * use client wait or fail * create broker directly * removed the unused import Co-authored-by: Matt Moore <mattmoor@vmware.com>
* adding istion annotation (knative#3534) (knative#3557) * adding istion annotation (knative#3534) * backporting knative#3543 * Update test/lib/duck/resource_inspectors.go Co-authored-by: Matt Moore <mattmoor@vmware.com> * Use the standard resource creation libs for upgrade tests. (knative#3539) * try to dump some state * use client wait or fail * create broker directly * removed the unused import Co-authored-by: Matt Moore <mattmoor@vmware.com> * cp 3897 (knative#3902) * cp 3897 * backport 3719 * x bit * apiserversource v1beta1->v1alpha2 * install broker / sugar * backport 3945 to .16 (knative#3948) Co-authored-by: VijayaSenaReddy Ayyappaneni <48216363+vayyappaneni@users.noreply.github.com> Co-authored-by: Matt Moore <mattmoor@vmware.com> Co-authored-by: Ville Aikas <11279988+vaikas@users.noreply.github.com>
Fixes #3532
backport #3534
backport #3542
backport #3543
backport #3539
Proposed Changes
Release Note