-
Notifications
You must be signed in to change notification settings - Fork 39.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
Include BGPConfiguration #71868
Include BGPConfiguration #71868
Conversation
Needed for calico 2.x to 3.x upgrade.
Hi @satyasm. Thanks for your PR. I'm waiting for a kubernetes 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 @caseydavenport |
/ok-to-test |
/cc @jingax10 |
/priority critical-urgent |
Looks like a dupe of this guy: #71682 :D I'll close mine |
/lgtm |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: caseydavenport, jingax10, satyasm 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 |
/retest |
2 similar comments
/retest |
/retest |
/retest Review the full test history for this PR. Silence the bot with an |
…8-upstream-release-1.12 Include BGPConfiguration
…8-upstream-release-1.13 Include BGPConfiguration
…8-upstream-release-1.11 Automated cherry pick of #71868: Include BGPConfiguration
Needed for calico 2.x to 3.x upgrade.
What type of PR is this?
What this PR does / why we need it:
Without this, k8s upgrades that go from older to newer version of calico break.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: