Add documentation guide for how to implement a bootstrap provider

[detiber]

What steps did you take and what happened:

With #1545 we will no longer be able to point folks interested in creating a bootstrap provider towards CABPK as a reference implementation. We need to provide a replacement for this (could be docs, could be a test reference implementation, etc). The replacement should be sufficient to get started with a bootstrap provider without having to disentangle what is CAPI related vs CABPK related in the cluster-api repo.

/kind documentation
/priority important-soon
/milestone v0.3.0

related to: #1090 #1138

[avorima]

I'd like to tackle this. My plan is to add a reference implementation under bootstrap/example.

[detiber]

@avorima while I think it might be possible to do a full reference implementation as a submodule, I think it might be a bit too easy to accidentally re-use some of the top level tooling. It might be better to take a documentation first approach like this PR is doing for infrastructure providers: #1682

[avorima]

Good point. I'm using the CAPI docs/**/*.md files for a lot of reference as well. I'll write some docs then.

[ncdc]

@avorima are you still interested in working on this?

[avorima]

@ncdc Sorry for the late response. Yes, I'd still like to finish this.

Regarding the docs: IMO the initial steps for creating a bootstrap provider are implicitly documented in the implementer's guide for cluster providers. Should I assume the reader is aware of this and focus on the steps that are specific to bootstrap providers or should it be a self-contained section?

[ncdc]

@avorima I'm tempted to say self-contained, or find some way to reorganize the cluster one so that there's a common section and then sections specific to cluster & bootstrap providers. @vincepri wdyt?

[vincepri]

This should be potentially an extension of the current guide we already have today https://cluster-api.sigs.k8s.io/developer/providers/implementers-guide/overview.html

[vincepri]

/area bootstrap

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[vincepri]

/lifecycle frozen

[vincepri]

/close

https://cluster-api.sigs.k8s.io/developer/providers/bootstrap.html

[k8s-ci-robot]

@vincepri: Closing this issue.

In response to this:

/close

https://cluster-api.sigs.k8s.io/developer/providers/bootstrap.html

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.