-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
Move the ComponentConfig types to staging KEP to implementable #2515
Conversation
From sig cloud-provider pov, these updates look fine to me. I'll defer to anything that @andrewsykim or @jagosan pick up on, though. |
* Set up staging publishing bot (async, non-critical) | ||
* The kubelet, kube-proxy and controller-manager follow, each one independently. | ||
* The kubelet, kube-proxy and kube-controller-manager types follow, each one independently. |
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.
kube+cloud-controller-manager
Looks good. |
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.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: timothysc 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 |
Move the ComponentConfig types to staging KEP to implementable
Some minor changes to the initial KEP after further discussions in the sig-api-machinery Slack channel.
Builds on top of #2354 and marks it as
implementable
.We have now submitted and merged the ~5 first PRs of this effort, with more PRs planned and in the reviewing stage. We hope to get all of this implemented by v1.12 code freeze.
The additions to this version is that we've decided on a defaulting story, and know a bit more about the actual implementation plan, and know what tests to write up for the MVP.
Again, mentioning the SIGs that are affected by this proposal:
@kubernetes/sig-cluster-lifecycle-pr-reviews @kubernetes/sig-api-machinery-pr-reviews @kubernetes/sig-architecture-api-reviews @kubernetes/sig-node-pr-reviews @kubernetes/sig-cloud-provider-pr-reviews @kubernetes/sig-scheduling-pr-reviews @kubernetes/sig-network-pr-reviews
/assign @thockin @jbeda @liggitt @bgrant0607 @mtaufen @wojtek-t