Enhancement/Bug Fix: Update OCI provider nodepool and error propagation and tests #8840
+316
−160
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind bug
/kind feature
What this PR does / why we need it:
This PR improves how the OCI Provider handles node errors.
OOC/LimitExceeded nodes (without instance IDs) and OKE InstanceCreating placeholder nodes should not be expected to register in the cluster and should be excluded from the expectedToRegister flow. (see the expectedToRegister flow in clusterstate.go), they should be handled in
fixNodeGroupSizeflowNodes with instance IDs (e.g., registration timeouts & NPN errors) are handled in
deleteCreatedNodesWithErrors.ErrorInfo is set when:
Since DECREASE_TARGET_CHECK_VIA_COMPUTE needs to call Compute, and this is not recommended in production per our discussion offline, this PR can handle OOC/LimitExceeded nodes without using the variable and additional calls.
This behavior is consistent with the intended autoscaler core logic.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
The change has been released in production for several months[https://bitbucket.oci.oraclecorp.com/projects/OMK/repos/autoscaler/pull-requests/6/overview] and has achieved stable scaling behavior based on the customer set timeout.
Does this PR introduce a user-facing change?
None
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: