Skip to content

Document static provisioning workflow (and for migrating v1a1 -> v1a2) #156

@BlaineEXE

Description

@BlaineEXE

Enhancement

Why is this needed?:

Firstly, the static provisioning workflow will be important for users, and it should be documented.

Specifically, users of COSI v1a1 will likely want a migration path from v1a1 to v1a2.

Describe the solution you'd like in detail:

Document an end-to-end how-to for the static workflow.

Relatedly (possibly separate), make sure the static workflow is tested in CI. Using the same example manifests in CI and in documentation is recommended as well, if possible through reasonable effort.

Describe alternatives you've considered:
N/A

Additional context:

Related KEP comment: kubernetes/enhancements#4599 (review)

Metadata

Metadata

Assignees

No one assigned

    Labels

    api/v1alpha2Issue reported against or feature request for v1alpha2 APIkind/documentationCategorizes issue or PR as related to documentation.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions