Bootstrapping Clusters with CAPI Infrastructure Providers

[patrickdillon]

This enhancement discusses how openshift-install can use cluster-api (CAPI) providers to provision cluster infrastructure,
without requiring access to an external management cluster or a local container runtime. By running a Kubernetes control plane and CAPI-provider controllers as subprocesses on the installer host, openshift-install can use CAPI and its
providers in a similar manner to how Terraform and its providers are currently being used.

[dhellmann]

Good doc. Lots of questions, still, as is expected for an early draft.

[patrickdillon]

cc @sdodson @2uasimojo @jnpacker @dtantsur @mdbooth @rvanderp3 @enxebre @jcpowermac @wking

[patrickdillon]

Added an Infrastructure Provisioning section. There is pending feedback that I will address after the holidays.

[patrickdillon]

@sdodson @2uasimojo @mhrivnak @jnpacker @dtantsur @mdbooth @rvanderp3 @jcpowermac @enxebre @dhellmann @avishaytAll feedback has been addressed and the enhancement updated. PTAL

@zaneb We would like to get this merged. Perhaps we can set a deadline of a week for reviewers to take a look.

[openshift-bot]

Inactive enhancement proposals go stale after 28d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Mark the proposal as fresh by commenting /remove-lifecycle stale.
Stale proposals rot after an additional 7d of inactivity and eventually close.
Exclude this proposal from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[patrickdillon]

/remove-lifecycle stale

/assign @zaneb

[openshift-bot]

Inactive enhancement proposals go stale after 28d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Mark the proposal as fresh by commenting /remove-lifecycle stale.
Stale proposals rot after an additional 7d of inactivity and eventually close.
Exclude this proposal from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[openshift-bot]

Stale enhancement proposals rot after 7d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Mark the proposal as fresh by commenting /remove-lifecycle rotten.
Rotten proposals close after an additional 7d of inactivity.
Exclude this proposal from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten enhancement proposals close after 7d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Reopen the proposal by commenting /reopen.
Mark the proposal as fresh by commenting /remove-lifecycle rotten.
Exclude this proposal from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closed this PR.

In response to this:

Rotten enhancement proposals close after 7d of inactivity.

See https://github.com/openshift/enhancements#life-cycle for details.

Reopen the proposal by commenting /reopen.
Mark the proposal as fresh by commenting /remove-lifecycle rotten.
Exclude this proposal from closing again by commenting /lifecycle frozen.

/close

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.

[patrickdillon]

/reopen

[openshift-ci]

@patrickdillon: Reopened this PR.

In response to this:

/reopen

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-sigs/prow repository.

[zaneb]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zaneb

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [zaneb]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sdodson]

/lgtm
/override ci/prow/markdownlint
Going ahead and getting this merged since most of the work has landed and removal of large portions of old implementation is imminent, if there's anything outdated and no longer accurate lets see to it that it gets updated.

[openshift-ci]

@sdodson: Overrode contexts on behalf of sdodson: ci/prow/markdownlint

In response to this:

/lgtm
/override ci/prow/markdownlint
Going ahead and getting this merged since most of the work has landed and removal of large portions of old implementation is imminent, if there's anything outdated and no longer accurate lets see to it that it gets updated.

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-sigs/prow repository.

[openshift-ci]

@patrickdillon: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.