rancher / dashboard

The Rancher UI
https://rancher.com
Apache License 2.0
456 stars 258 forks source link

Add ability to modify volumeType when creating rke1 or rke2 downstream clusters #5815

Open ronhorton opened 2 years ago

ronhorton commented 2 years ago

Setup

Describe the bug attempted to add a downstream rke1 cluster using ami-0d3c317f604c2c84c (user: suse) and the cluster never provisioned. Required editing the node template to have volumeType: gp3. There's no way to actually do this when creating a downstream cluster via ui - had to edit the nodetemplate with api

To Reproduce

  1. create downstream cluster
  2. ami-0d3c317f604c2c84c
  3. user: suse
  4. 1 etcd, 1 controlplane, 3 workers
  5. click create

Result cluster appears on the cluster management page, but never completes provisioning. error: error syncing 'c-28h92/m-jhq8r': handler node-controller: Error creating machine: Error in driver during machine creation: Error launching instance: InvalidParameterCombination: The parameter iops is not supported for gp2 volumes., requeuing

Expected Result cluster provisions successfully

Screenshots

Additional context

Detailed Description

Context

nwmac commented 2 years ago

I assume this is on Amazon?

catherineluse commented 1 year ago

I wonder if the problem is that that storage option has certain requirements on the cloud provider side. So we need to know the cloud provider and read their storage documentation to be sure that that storage type is compatible with other settings in the node template.

skanakal commented 1 year ago

https://aws.amazon.com/blogs/database/understanding-burst-vs-baseline-performance-with-amazon-rds-and-gp2/ `

The gp2 storage type also has a base IOPS that is set when the volume is created. However, you don’t provide a value for the IOPS directly—`

By default the volumeType sets to gp2 and there seems to be the iops value also picked which is unsupported. And there is no way to mention the volumeType while creating the RKE1 or RKE2 downstream clusters like here https://github.com/rancher/rancher/issues/22898.

To workaround this, need to update node template thru API https:///v3/nodeTemplates/ and there is no option in the UI.