Issue #18 - Feature to configure autoscaler block and attributes for spotinst-ocean-eks #19
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.
Currently ocean-eks module defaults autoscaler configuration to automatic configuration when enabled. The autoscaler is also enabled by default.
The purpose of this issue is to add some flexibility to spotinst/ocean-eks module to make use of the ability to configure autoscaler available in the spotinst_ocean_aws resource.
This gives us infrastructure designers and engineers using spotinst to develop ocean clusters configurable for autoscalers' headroom, cooldown and resource limits and even pass on values to ocean's virtual node groups
The following vars have been introduced that can be added to ocean-eks module to achieve this