feat: Add support for deletion protection functionality in the cluster #3475
+8
−0
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
This PR adds support for EKS cluster deletion protection configuration through a new
enable_deletion_protection
variable. This feature allows users to enable AWS's built-in deletion protection safeguard for EKS clusters, helping prevent accidental or unauthorized deletion of critical infrastructure.The variable defaults to false to maintain backward compatibility with existing module usage.
Motivation and Context
EKS cluster deletion protection is already a supported feature in AWS, providing a valuable security safeguard that helps prevent accidental deletion of critical Kubernetes infrastructure. This enhancement addresses user requests for better operational safety and aligns with AWS security best practices.
Dependency: This PR requires the AWS Terraform provider to support managing EKS deletion protection through Terraform. While AWS already supports this functionality natively, the Terraform provider implementation is pending in the following PR. This module enhancement will be ready to use once that provider update is released.
Breaking Changes
None. This is a backward-compatible addition. The new enable_deletion_protection variable defaults to false, preserving existing behavior for current module users.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request