Skip to content
Permalink
Browse files

check off some items from the roadmap

  • Loading branch information
BenTheElder committed Jan 17, 2020
1 parent aec4d1c commit 028dccbecd774dfb01dba263a0f117000665fa20
Showing with 10 additions and 6 deletions.
  1. +10 −6 site/content/docs/contributing/1.0-roadmap.md
@@ -21,7 +21,7 @@ To reach "beta" [grade][deprecation-policy] kind needs to at minimum:

- [x] Improve documentation (Though this will eternally be "In Progress" !)
- [X] create a documentation site - [#268]
- [ ] expand examples of using kind
- [x] expand examples of using kind (We can always use more, but we have more of this now)
- [x] cover known issues, debugging, work-arounds, etc.
- [x] Reliably [pass][kind-conformance-dashboard] the Kubernetes [conformance tests]
- [x] [Certify][certified] Conformance
@@ -33,22 +33,26 @@ To reach "beta" [grade][deprecation-policy] kind needs to at minimum:
- [x] add Windows binaries to releases - [#155]
- [x] improve instructions for KUBECONFIG in particular
- [ ] Support usage as a properly versioned, supported, and documented library. This includes following semver without every release being a major / breaking change to the API (which must be extensible without breakage), ensuring the CLI only uses a suitable public library surface, documentation and examples for the library, versioned types for public APIs (E.G. config format), etc.
- [ ] should be possible to troubleshoot kind without needing to modify kind or use external debugging tools
- [ ] consistent logging (what is logged, when should it be logged, what levels are used)
- [ ] errors have appropriate context
- TODO: what exactly do we want here? Should this really be beta blocking?
- [x] should be possible to troubleshoot kind without needing to modify kind ~or use external debugging tools~ (this should be possible now, if not perfect!)
- x ] consistent logging (what is logged, when should it be logged, what levels are used) (this is consistent-ish now, if not perfect)
- [x] errors have appropriate context (this is debateable and never perfect, but improved a lot, especially if you use `-v 1` or greater)
for managing clusters in test harnesses
- [ ] move API types / labels from `*.k8s.io` into [`*.x-k8s.io`][api-review-voluntary]
- [x] move API types / labels from `*.k8s.io` into [`*.x-k8s.io`][api-review-voluntary]
- [x] Support all currently [upstream-supported Kubernetes versions][version-skew-policy]

## GA Requirements

To reach "GA" [grade][deprecation-policy] kind needs to at minimum:

- [ ] Support non-AMD64 architectures (namely ARM) - [#166]
- TODO: move this to post GA? This is expensive and has relatively low demand so far.
- [ ] Automated publishing of Kubernetes release based kind "node" images - [#197]
- [ ] Support for runtimes other than docker/default including podman, ignite etc.
- TODO: moves this to post GA? We can probably do this without breaking anyone and the demand is low-ish.
- [ ] Enable audit-logging
- [ ] First class support for skewed node (Kubernetes) versions
- TODO: should this be post-GA? this could probably be an extension
- [x] First class support for skewed node (Kubernetes) versions (I beleive this is relatively first-class now, things should work fine if you specify different node images)
- ... TBD, more will be added here ...

## Non-Goals

0 comments on commit 028dccb

Please sign in to comment.
You can’t perform that action at this time.