-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
autoscaler for cluster xxxxxx might already exists. #12
Comments
The resource on TF is already prepared. However, the autoscaler functionality is not yet available publicly for HCP |
@davivcgarcia No, this is a cluster autoscaler. That one currently in the UI is the autoscaling parameters for the initial instance pool for customer workload that you get when installing the cluster. The cluster autoscaler has many more options in comparison to min and max nodes The configuration for instance pools is available through the machine pool resource |
@gdbranco Do you have an example of how to setup the default worker machine pool autoscaling parameters at cluster creation? And what is the difference between the cluster autoscaler and the autoscaling parameters from the machine pools? |
Hello i am having this issue to create a hcp cluster with autoscale enable
module.rosa_cluster_hcp.rhcs_cluster_rosa_hcp.rosa_hcp_cluster: Modifying... [id=2as8ja8fdlblueccm19sehb6s6d0m40t]
module.rosa_cluster_hcp.rhcs_cluster_rosa_hcp.rosa_hcp_cluster: Modifications complete after 1s [id=2as8ja8fdlblueccm19sehb6s6d0m40t]
module.rosa_cluster_hcp.rhcs_hcp_cluster_autoscaler.cluster_autoscaler[0]: Creating...
Error: Can't create autoscaler
with module.rosa_cluster_hcp.rhcs_hcp_cluster_autoscaler.cluster_autoscaler[0],
on .terraform/modules/rosa_cluster_hcp/modules/rosa-cluster-hcp/main.tf line 113, in resource "rhcs_hcp_cluster_autoscaler" "cluster_autoscaler":
113: resource "rhcs_hcp_cluster_autoscaler" "cluster_autoscaler" {
Autoscaler for cluster '2as8ja8fdlblueccm19sehb6s6d0m40t' might already
exists. Error: status is 403, identifier is '403', code is
'CLUSTERS-MGMT-403' and operation identifier is
'76f0df43-0be9-434d-8f1e-3cd1f4ae4c01': Autoscaler configuration is not
available
The text was updated successfully, but these errors were encountered: