mirror of
https://github.com/ysoftdevs/terraform-aws-eks.git
synced 2026-03-23 18:01:04 +01:00
Use kubernetes provider to manage aws auth (#355)
This commit changes the way aws auth is managed. Before a local file was used the generate the template and a null resource to apply it. This is now switched to the terraform kubernetes provider.
This commit is contained in:
committed by
Max Williams
parent
b69c8fb759
commit
9363662574
14
docs/upgrading-to-aws-auth-kubernetes-provider.md
Normal file
14
docs/upgrading-to-aws-auth-kubernetes-provider.md
Normal file
@@ -0,0 +1,14 @@
|
||||
# Upgrading from version <= 7.x to 8.0.0
|
||||
|
||||
In version 8.0.0 the way the aws-auth config map in the kube-system namespaces is managed, has been changed.
|
||||
Before this was managed via kubectl using a null resources. This was changed to be managed by the terraform kubernetes
|
||||
provider.
|
||||
|
||||
To upgrade you have to add the kubernetes provider to the place you are calling the module. You can see examples in
|
||||
the [examples](../examples) folder.
|
||||
You also have to delete the aws-auth config map before doing an apply.
|
||||
|
||||
**This means you need to the apply with the same user/role that created the cluster.**
|
||||
|
||||
Since this user will be the only one with admin on the k8s cluster. After that the resource is managed trough the
|
||||
terraform kubernetes provider.
|
||||
Reference in New Issue
Block a user