+++ This bug was initially created as a clone of Bug #2062310 +++

+++ This bug was initially created as a clone of Bug #2062290 +++

+++ This bug was initially created as a clone of Bug #2062007 +++

Description of problem:

The `machine-config-controller bootstrap` subcommand uses the `--template` flag default value, but the flag is only associated with the `start` subcommand internally, so end users can't actually override the hard-coded default value when running the `bootstrap` command.

Version-Release number of MCO (Machine Config Operator) (if applicable):

Platform (AWS, VSphere, Metal, etc.): All

Are you certain that the root cause of the issue being reported is the MCO (Machine Config Operator)?
(Y/N/Not sure): Y

How reproducible:

Run `machine-config-controller bootstrap --template`.

Did you catch this issue by running a Jenkins job? If yes, please list: No

Steps to Reproduce:

Run `machine-config-controller bootstrap --template ...`.

Actual results:

Command fails because the `--template` flag is unrecognized.

Expected results:

Should work with the value I provided.

Additional info:

This was encountered performing integration work for HyperShift.