Skip to content

Commit cd94ed9

Browse files
committed
update readme
1 parent 6852542 commit cd94ed9

File tree

2 files changed

+21
-0
lines changed

2 files changed

+21
-0
lines changed

_examples/eks/README.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -55,3 +55,14 @@ terraform apply -var=workers_count=4 -var=workers_type=m4.xlarge
5555
## Additional configuration of EKS
5656

5757
To view all available configuration options for the EKS module used in this example, see [terraform-aws-modules/eks docs](https://registry.terraform.io/modules/terraform-aws-modules/eks/aws/latest).
58+
59+
## Replacing the EKS cluster and re-creating the Kubernetes / Helm resources
60+
61+
When the cluster is initially created, the Kubernetes and Helm providers will not be initialized until authentication details are created for the cluster. However, for future operations that may involve replacing the underlying cluster (for example, changing VM sizes), the EKS cluster will have to be targeted without the Kubernetes/Helm providers, as shown below. This is done by removing the `module.kubernetes-config` from Terraform State prior to replacing cluster credentials, to avoid passing outdated credentials into the providers.
62+
63+
This will create the new cluster and the Kubernetes resources in a single apply.
64+
65+
```
66+
terraform state rm module.kubernetes-config
67+
terraform apply
68+
```

_examples/gke/README.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -64,3 +64,13 @@ gcloud container clusters get-credentials $(terraform output cluster_name|jq -r)
6464
kubectl get pods -n test
6565
```
6666

67+
## Replacing the GKE cluster and re-creating the Kubernetes / Helm resources
68+
69+
When the cluster is initially created, the Kubernetes and Helm providers will not be initialized until authentication details are created for the cluster. However, for future operations that may involve replacing the underlying cluster (for example, changing VM sizes), the GKE cluster will have to be targeted without the Kubernetes/Helm providers, as shown below. This is done by removing the `module.kubernetes-config` from Terraform State prior to replacing cluster credentials, to avoid passing outdated credentials into the providers.
70+
71+
This will create the new cluster and the Kubernetes resources in a single apply.
72+
73+
```
74+
terraform state rm module.kubernetes-config
75+
terraform apply
76+
```

0 commit comments

Comments
 (0)