Allow cluster creation without default-worker nodegroup
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Magnum |
New
|
Undecided
|
Unassigned | ||
Bug Description
When creating a new Kubernetes cluster, one has to specify flavor_id/image_id which are then used to create the default-worker nodegroup.
If operators later want to modify those parameters, they have to create the cluster (e.g. the Terraform provider has those fields marked as ForceNew and a `openstack coe nodegroup update` returns '/flavor_id' is an internal attribute and can not be updated).
If node_count=0 is specified, the default-worker nodegroup is still created (albeit with no workers). This can cause confusion for operators if they have no intention to use that nodegroup (one reason being that changing the flavor_id/image_id will require creating the cluster). It seems the default-worker nodegroup is a handicapped nodegroup.
It would be nice if a cluster could be created without this default-worker nodegroup in case operators want to manage the nodegroups themselves.
