Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
KEP for Azure Availability Zones #2364
The KEP adds Azure Availability Zones support to Kubernetes, which includes:
thockin left a comment
It's not clear to me - is this proposing changes to Kubernetes concepts or adding new labels, or is it just changing the Azure implementation with no impact to the rest of the system?
I'm not sure that changes that stay within the azure implementation need a KEP?
Hey @thockin good question. The KEP process is somewhat vague on what constitutes a KEP:
I think that it is clearly within the scope of a SIG to track something as a KEP if they want too:
"As the local bodies of governance, SIGs should have broad latitude in describing what constitutes an enhancement which should be tracked through the KEP process."
But it's also clear that I don't think that this meets the guidelines for things that are required to be a KEP:
"any technical effort (refactoring, major architectural change) that will impact a large section of the development community should also be communicated widely. The KEP process is suited for this even if it will have zero impact on the typical user or operator."
"Enhancements that have major impacts on multiple SIGs should use the KEP process."
So I guess given that this KEP has been started, we may as well finish it, but going forward SIG-Azure will develop guidelines for what should and should not be a KEP
"SIGs may find that helpful to enumerate what does not require a KEP rather than what does."
So from a Features Maintainer perspective, Feature Owners are required to submit design proposals for units of work that qualify as Features i.e., those tracked within
From SIG Azure Chair perspective, anything that moves us along the line of transparency w.r.t. SIG roadmap is a step in the right direction.
That said, I'm happy to firm up guidelines on expectations for KEP submission in SIG Azure! :)
referenced this pull request
Jul 24, 2018
[APPROVALNOTIFIER] This PR is APPROVED
The full list of commands accepted by this bot can be found here.
The pull request process is described here