Many times when people try to follow the Cluster API Quick Start tutorial, they execute steps designed for the Docker provider that presumes we have a development flavor. If we add a development flavor, we can avoid folks hitting the error.
Detailed Description
I think it'll just be a copy of the normal cluster template but we could take out options (like limiting it to 1 control plane node) so there's fewer variables to think about changing. I'm not sure that reduction in options would actually reduce friction or cause problems in the future if they wanted to add nodes to the cluster.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
User Story
Many times when people try to follow the Cluster API Quick Start tutorial, they execute steps designed for the Docker provider that presumes we have a development flavor. If we add a development flavor, we can avoid folks hitting the error.
Detailed Description
I think it'll just be a copy of the normal cluster template but we could take out options (like limiting it to 1 control plane node) so there's fewer variables to think about changing. I'm not sure that reduction in options would actually reduce friction or cause problems in the future if they wanted to add nodes to the cluster.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
/kind feature