-
Notifications
You must be signed in to change notification settings - Fork 6.6k
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
Fixes issue #7573 - Made Calico permissions compatible with v3.18.x #7575
Fixes issue #7573 - Made Calico permissions compatible with v3.18.x #7575
Conversation
… with v3.18.x (see projectcalico/calico#4557). Specifically, granted watch to custom resources blockaffinities, ipamblocks & ipamhandles
Hi @holmesb. Thanks for your PR. I'm waiting for a kubernetes-sigs 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. |
/ok-to-test |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: floryut, holmesb 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 |
/lgtm |
… with v3.18.x (see projectcalico/calico#4557). Specifically, granted watch to custom resources blockaffinities, ipamblocks & ipamhandles (kubernetes-sigs#7575)
* Add Calico v3.17.3 and v3.18.1 (kubernetes-sigs#7524) * add hashes for calico v3.17.3 * add hashes for claico v3.18.1 * bump default calico version to v3.17.3 * calico crds are missing yaml separator breaking kdd * Calico new versions v3.17.4 and v3.18.2 (kubernetes-sigs#7563) * calico: upgrade from v3.17.3 to v3.17.4 * calico: upgrade from v3.18.1 to v3.18.2 * Fixes issue kubernetes-sigs#7573 - Made Calico permissions compatible with v3.18.x (see projectcalico/calico#4557). Specifically, granted watch to custom resources blockaffinities, ipamblocks & ipamhandles (kubernetes-sigs#7575) * bump calico 3.18 to v3.18.3 (kubernetes-sigs#7592) * Support Calico advertisement of MetalLB LoadBalancer IPs (kubernetes-sigs#7593) * add initial MetalLB docs * metallb allow disabling the deployment of the metallb speaker * calico>=3.18 allow using calico to advertise service loadbalancer IPs * Document the use of MetalLB and Calico * clean MetalLB docs Co-authored-by: Cristian Calin <[email protected]> Co-authored-by: holmesb <[email protected]>
… with v3.18.x (see projectcalico/calico#4557). Specifically, granted watch to custom resources blockaffinities, ipamblocks & ipamhandles (kubernetes-sigs#7575)
… with v3.18.x (see projectcalico/calico#4557). Specifically, granted watch to custom resources blockaffinities, ipamblocks & ipamhandles (kubernetes-sigs#7575)
See projectcalico/calico#4557. Specifically, granted watch to custom resources: blockaffinities, ipamblocks & ipamhandles.
What type of PR is this?
What this PR does / why we need it:
Existing permissions cause a "connection is unauthorized" message to be logged many times per second by pod: kube-system/calico-kube-controllers
Which issue(s) this PR fixes:
Fixes #7573
Does this PR introduce a user-facing change?: