Description
Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Hello!
As of today, when we bump the version of a K8s cluster, upgrade_pools is always sent as True. This parameter is defined here in the K8s API: https://www.scaleway.com/en/developers/api/kubernetes/#path-clusters-upgrade-a-cluster
This is probably a healthy default, but depending on the exact Kubernetes setup being used, it may cause issues. Typically, some local data can be lost in the process, which is why there's a warning when enabling this parameter from the console. So users may want to pass upgrade_pools: False to the underlying API call.
The current workaround is to do the upgrade outside of Terraform, and then apply the changes to reconcile the configuration with the infra. This is OK, but it would be nice to be able to do everything from Terraform.
Thanks!
New or Affected Resource(s)
- scaleway_k8s_cluster
Potential Terraform Configuration
(Please validate this with the K8s team ^^)
resource "scaleway_k8s_cluster" "cluster" {
...
upgrade_pools_on_version_changes = false // true by default, optional to keep existing behavior
}References
- #0000