-
Notifications
You must be signed in to change notification settings - Fork 39.2k
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
allow failed discovery on initial quota controller start #67784
allow failed discovery on initial quota controller start #67784
Conversation
/sig api-machinery |
This PR is not for the master branch but does not have the |
/assign @mbohlool |
/test pull-kubernetes-e2e-gce |
Can you add a release note to the original PR? Note you added in the first comment of this PR looks to be a good candidate: |
Thanks for adding release notes. Approved for cherrypick. |
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: cheftako 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 |
Applying lgtm/approval from the base PR |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. |
Cherry pick of #67433 on release-1.9.
#67433: allow failed discovery on initial quota controller start
kube-controller-manager can now start the quota controller when discovery results can only be partially determined.