-
Notifications
You must be signed in to change notification settings - Fork 202
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
Terraform apply after changing max_pods_per_node does not take effect #876
Comments
@bettaps / @hyder / @devoncrouse - This looks like a provider bug. There's a similar issue opened here -oracle/terraform-provider-oci#2011. The terraform apply for autoscaler_pool completes without actually changing the value for max_pods_per node but fails for oke-vm-standard pool.
@bettaps / @hyder / @devoncrouse - Any feedback ? |
Community Note
Terraform Version and Provider Version
Terraform v1.4.2
Affected Resource(s)
oci_containerengine_node_pool
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
Using oke module, we wanted to change the value of max_pods_per_node from 110 to 15, after terraform apply it has to update this value on the nodepool.
Actual Behavior
In terraform plan it shows that it needs to be updated, but after doing the apply, the node pool configuration does not get updated. When you do terraform plan again, it shows that the parameter has not changed.
Steps to Reproduce
terraform apply
Important Factoids
References
The text was updated successfully, but these errors were encountered: