feat(cluster): add encryptionConfigKeyArn opt to encrypt k8s Secrets #389
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.
Proposed changes
EKS supports envelope encryption for Kubernetes Secrets that use an AWS
KMS key to sign the Secrets in etcd.
A new cluster option
encryptionConfigKeyArn
is being added that allowsthe configuration of a KMS key ARN to be provided for establishing the
cluster's encryption configuration.
Note: the encryption configuration becomes a core part of the cluster's
configuration. Any changes to its settings will require rebuilding a new cluster
and nodes.
See for more details from AWS.
Related issues (optional)
Closes #384