-
Notifications
You must be signed in to change notification settings - Fork 213
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
nodepool.tf|precondition bug|single availability domain must be specified when using a capacity reservation #882
Comments
@shb-mll / @hyder / @devoncrouse - The current code for oci_containerengine_node_pool works fine for single availability domain regions. Capacity reservation is an availability domain specific resource which means for node placement in capacity reservation across three availability domains (in regions like us-ashburn-1), the worker_capacity_reservation_id input should have provision to accept 3 such capacity reservation ids with mapping to right availability domain.
So it doesn’t support capacity reservation ids for multiple availability domain regions. Till we have this feature rolled out, it’s better to change the precondition error message stating that the capacity reservation cannot be used for regions with multiple availability domains.
The implementation requires correctly mapped key value input (availability_domain:capacity_reservation_id) for worker_capacity_reservation_id that can be consumed in oci_containerengine_node_pool to place nodes in respective capacity reservations @shb-mll / @hyder / @devoncrouse - Any feedback ? |
Or we can pick an AD by default and allow the user to change? |
@hyder Can you please explain in detail what do you mean by picking up an AD? The ADs are automatically gathered and cannot be input by user. Not sure how the user would map AD and capacity reservation as an input. |
I was wondering if we can pick the 1st AD by default but allow the user to change the default. @devoncrouse what you think? |
@hyder - I think for multi ad region, we can map the capacity_reservation_id to first AD by default, provided the user always provide the capacity_reservation_id from first AD (which can be documented) |
Community Note
Terraform Version and Provider Version
$ terraform --version
Terraform v1.3.9
on darwin_arm64
Affected Resource(s)
oci_containerengine_node_pool
Terraform Configuration Files
https://github.com/oracle-terraform-modules/terraform-oci-oke/blob/v5.1.0/modules/workers/nodepools.tf#L146
Debug Output
Panic Output
Expected Behavior
the precondition should only check when a capacity reservation is specified. However its check for all cases.
The condition should be changed to below
Actual Behavior
Its checking irrespective of capacity reservation id specification. In my case the capacity reservation id is default value null.
Steps to Reproduce
Important Factoids
References
The text was updated successfully, but these errors were encountered: