Project: Karmada (Orchestration & Management / Scheduling & Orchestration)
File: proposal-template.md

title: Your short, descriptive title authors: "@robot" # Authors' github accounts here. reviewers: "@robot" TBD approvers: "@robot" TBD creation-date: yyyy-mm-dd <!-- This is the title of your KEP. Keep it short, simple, and descriptive. A good title can help communicate what the KEP is and should be considered as part of any review. --> <!-- This section is incredibly important for producing high-quality, user-focused documentation such as release notes or a development roadmap. A good summary is probably at least a paragraph in length. --> <!-- This section is for explicitly listing the motivation, goals, and non-goals of this KEP. Describe why the change is important and the benefits to users. --> <!-- List the specific goals of the KEP. What is it trying to achieve? How will we know that this has succeeded? --> <!-- What is out of scope for this KEP? Listing non-goals helps to focus discussion and make progress. --> <!-- This is where we get down to the specifics of what the proposal actually is. This should have enough detail that reviewers can understand exactly what you're proposing, but should not include things like API designs or implementation. What is the desired outcome and how do we measure success?. The "Design Details" section below is for the real nitty-gritty. --> <!-- Detail the things that people will be able to do if this KEP is implemented. Include as much detail as possible so that people can understand the "how" of the system. The goal here is to make this feel real for users without getting bogged down. --> <!-- What are the caveats to the proposal? What are some important details that didn't come across above? Go in to as much detail as necessary here. This might be a good place to talk about core concepts and how they relate. --> <!-- What are the risks of this proposal, and how do we mitigate? How will security be reviewed, and by whom? How will UX be reviewed, and by whom? Consider including folks who also work outside the SIG or subproject. --> <!-- This section should contain enough information that the specifics of your change are understandable. This may include API specs (though not always required) or even code snippets. If there's any ambiguity about HOW your proposal will be implemented, this is the place to discuss them. --> <!-- Note: Not required until targeted at a release. Consider the following in developing a test plan for this enhancement: Will there be e2e and integration tests, in addition to unit tests? How will it be tested in isolation vs with other components? No need to outline all test cases, just the general strategy. Anything that would count as tricky in the implementation, and anything particularly challenging to test, should be called out. --> <!-- What other approaches did you consider, and why did you rule them out? These do not need to be as detailed as the proposal, but should include enough information to express the idea and why it was not acceptable. --> <!-- Note: This is a simplified version of kubernetes enhancement proposal template. https://github.com/kubernetes/enhancements/tree/3317d4cb548c396a430d1c1ac6625226018adf6a/keps/NNNN-kep-template -->