-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws configmap #3006
Comments
actually checking But if you have opinion/suggestions please let me know |
@Mieszko96 Do you know if there new method to handle who has auth to use the cluster? is it |
@kaykhan It has been moved to submodule |
This sub module is going to be removed in the next version (21) https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/docs/UPGRADE-20.0.md#%EF%B8%8F-upcoming-changes-planned-in-v210-%EF%B8%8F So just curious how to handle it moving forward. Im wondering if we should now be creating this resource ourselves. https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs/resources/config_map_v1 |
its a separate sub-module and the code has not changed for this functionality for several years. Even though the code will be removed in v21, theres nothing stopping you from using the sub-module at v20 for years to come. However, long term the strategy is to use cluster access entries |
This issue has been automatically marked as stale because it has been open 30 days |
This issue was automatically closed because of stale in 10 days |
hey in my current terraform i am using to manage aws configmap
i'm using module with version 19.20
with eks_managed_node_groups and
create_aws_auth_configmap = false
manage_aws_auth_configmap = false
What i need to do to switch to
manage_aws_auth_configmap = true
and remove resource "kubectl_manifest" "aws-auth-cm"
What i tested.
scenario 1
removed resource "kubectl_manifest" "aws-auth-cm"
manage_aws_auth_configmap = false -> true
❌ configmap was deleted( we don't have configmap in EKS)
scenario 2
removed resource "kubectl_manifest" "aws-auth-cm"
create_aws_auth_configmap = true
❌ ✅ this scenario works, but if i use same code for brand new EKS it have error aws-auth already exist.
And i need solution for updated exisiting terraform and for brand new.
scenario 3
Also tried with moved block, but getting error
This statement declares a move from kubectl_manifest.aws-auth-cm to
module.eks.kubernetes_config_map.aws_auth[0], which is a resource instance of
a different type.
or
module.eks.kubernetes_config_map_v1_data.aws_auth[0], which is a resource
instance of a different type.
I don't mind if solution require removing state from terraform list
The text was updated successfully, but these errors were encountered: