Closed
Description
Description
As part of the work to make installation/operation easier being done by sig-cluster-lifecycle, we are going to continue to make configuration more dynamic, through ongoing work on componentconfig.
Progress Tracker
- Before Alpha
- Write and maintain draft quality doc
- During development keep a doc up-to-date about the desired experience of the feature and how someone can try the feature in its current state. Think of it as the README of your new feature and a skeleton for the docs to be written before the Kubernetes release. Paste link to Google Doc: DOC-LINK
- Design Approval
- Design Proposal
- Identify shepherd: @mikedanese, @roberthbailey
- Write (code + tests + docs) then get them merged. ALL-PR-NUMBERS
- Code needs to be disabled by default. Verified by code OWNERS
- Minimal testing
- Minimal docs
- cc
@kubernetes/docs
on docs PR - cc
@kubernetes/feature-reviewers
on this issue to get approval before checking this off - New apis: Glossary Section Item in the docs repo: kubernetes/kubernetes.github.io
- cc
- Update release notes
- Write and maintain draft quality doc
- Before Beta
- Testing is sufficient for beta
- User docs with tutorials
- Updated walkthrough / tutorial in the docs repo: kubernetes/kubernetes.github.io
- cc
@kubernetes/docs
on docs PR - cc
@kubernetes/feature-reviewers
on this issue to get approval before checking this off
- Thorough API review
- cc
@kubernetes/api
- cc
- Before Stable
- docs/proposals/foo.md moved to docs/design/foo.md
- cc
@kubernetes/feature-reviewers
on this issue to get approval before checking this off
- cc
- Soak, load testing
- detailed user docs and examples
- cc
@kubernetes/docs
- cc
@kubernetes/feature-reviewers
on this issue to get approval before checking this off
- cc
- docs/proposals/foo.md moved to docs/design/foo.md
FEATURE_STATUS is used for feature tracking and to be updated by @kubernetes/feature-reviewers
.
FEATURE_STATUS: IN_DEVELOPMENT
More advice:
Design
- Once you get LGTM from a
@kubernetes/feature-reviewers
member, you can check this checkbox, and the reviewer will apply the "design-complete" label.
Coding
- Use as many PRs as you need. Write tests in the same or different PRs, as is convenient for you.
- As each PR is merged, add a comment to this issue referencing the PRs. Code goes in the http://github.com/kubernetes/kubernetes repository,
and sometimes http://github.com/kubernetes/contrib, or other repos. - When you are done with the code, apply the "code-complete" label.
- When the feature has user docs, please add a comment mentioning
@kubernetes/feature-reviewers
and they will
check that the code matches the proposed feature and design, and that everything is done, and that there is adequate
testing. They won't do detailed code review: that already happened when your PRs were reviewed.
When that is done, you can check this box and the reviewer will apply the "code-complete" label.
Docs
- Write user docs and get them merged in.
- User docs go into http://github.com/kubernetes/kubernetes.github.io.
- When the feature has user docs, please add a comment mentioning
@kubernetes/docs
. - When you get LGTM, you can check this checkbox, and the reviewer will apply the "docs-complete" label.
Metadata
Metadata
Labels
Categorizes issue or PR as related to a new feature.Categorizes an issue or PR as relevant to SIG API Machinery.Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.Denotes an issue tracking an enhancement targeted for Alpha statusDenotes an enhancement issue is NOT actively being tracked by the Release Team