convenient ability to just boot a coreos node with custom butane/ignition

[cgwalters]

I've had this desire a few times myself, most recently I wanted to point some users at this in https://issues.redhat.com/browse/OCPBUGS-1327

Basically when one wants to debug an IPI issue, it'd be really, really useful to have something like:

openshift-install provision-one-coreos --with-butane foo.bu

(And --with-ignition foo.ign)

That would use the relevant bits of the install-config.yaml and run through all the same Terraform setup code to set up basically the same flow for the bootstrap node and...that's it. The user would normally put a SSH key in the install config for this. (But with --with-butane one could inject one easily, alongside any other desired config)

This would make it much easier to debug e.g. networking issues between instances, verify hardware works etc. without entirely dropping to fully custom UPI.

[openshift-bot]

Issues go stale after 90d of inactivity.

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

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

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

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

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

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

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

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue 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.

[cgwalters]

/reopen
/lifecycle frozen

[openshift-ci]

@cgwalters: Reopened this issue.

In response to this:

/reopen
/lifecycle frozen

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.

[cgwalters]

This came up again in the context of testing custom OS images for https://docs.openshift.com/container-platform/4.12/post_installation_configuration/coreos-layering.html