Project Scope

    See also: the , and the 1.0 tracking milestone.

    Stakeholders:

    • kind maintainers
    • kind contributors

    Covered Work:

    • Releases & tooling
    • Automated image publishing
    • Documentation bootstrapping (IE this site)
    • Enough Kubernetes testing to test kind itself (Kubernetes Conformance tests)
    • Setting up linters and other tools to verify quality
    • Setting up a recurring subproject meeting

    P0: Support Testing Kubernetes

    Covered Work:

    • Limited workloads / e2e testing
    • Cluster bring-up (IE )
    • Kubernetes build (and currently install, but that may be problematic for cross-platform #166)
    • Node skew, client skew (kubectl / e2e versions)
    • Image publishing
    • Kubernetes CI tooling and
    • Most everything in the 1.0 roadmap
    • …

    Stakeholders: Various projects both inside & outside the Kubernetes Org.

    Covered Work:

    • Improve “kind as a library”
      • better and more controllable logging
      • generally more control over output
      • example usage & documentation
    • Most of the rest should be covered by improving “kind the binary” outlined above
    • …

    P2: Provide Cheap Bootstrap Clusters for the Cluster-API

    Stakeholders:

    Stakeholders:

    • Indeterminate / many

    Possibly supporting various things that we cannot reasonably test today including:

    • “node” tests, e.g. reboot
    • Upgrades, downgrades
    • Anything depending on ingress
    • Anything depending on persistent storage / PVs
    • Testing the cluster-api proper with some sort of machine provisioning
    • Device plugin, e.g. GPU
    • …

    Out of Scope

    Some things we can likely never cover in a reasonable way:

    • Cloud provider /
    • Some of the node testing (which portions exactly is currently unclear)
    • Being an alternative to “docker compose” etc.
    • Replacing Phippy ❤️ 🦒 ❤️
    • …