fix: Incorporate AWS provider v6.15
corrections for EKS Auto Mode to support enabling/disabling EKS Auto Mode without affecting non-Auto Mode users
#3526
+66
−49
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.
Description
enabled
fields of EKS Auto Mode configurations has been removed in this change. There is further work required on the EKS API to supply these values by default instead of empty fields/nil/null. With this change, the majority of users encountering issues where the diff shows changes for EKS Auto Mode when they are not using Auto Mode is resolved. There is still one edge case where users MUST setcompute_config.enabled = false
if they wish to disable Auto Mode (after enabling and provisioning) otherwise these changes will not be detected and Auto Mode will not be disabled as intended. Once users have applied the changes withcompute_config.enabled = false
, they can proceed to remove thecompute_config
block from their configurations. Again, this edge case should be resolved once the EKS API provides a default value for the other two fields (storage_config
andelastic_load_balancing
) required by EKS Auto Mode. A warning note has been added to the documentation for this edge caseMotivation and Context
Breaking Changes
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull requestTest Procedure
source
of the module is pointed to the changes contained in this PR. No changes are observed within the Terraform plan diff as expected:compute_config.enabled = false
and applying that change. See note above and within the README about trying to disable by simply removing thecompute_config
block from the configuration failing to correctly disable EKS Auto Mode due to the EKS API current limiations:compute_config
block can be removed and there are no changes detected on the Terraform plan diff: