kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Note that `kops rolling-update` is required after tf apply 

Closes https://github.com/kubernetes/kops/issues/4740
This commit is contained in:
Fabio Rehm 2018-04-29 19:50:55 -03:00 committed by GitHub
parent 4f8dcfe41d
commit 9efc769eb9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/terraform.md
View File

@ -88,6 +88,8 @@ $ terraform apply
Ps: You aren't limited to cluster edits i.e. `kops edit cluster`. You can also edit instances groups e.g. `kops edit instancegroup nodes|bastions` etc.
Keep in mind that some changes will require a `kops rolling-update` to be applied. When in doubt, run the command and check if any nodes needs to be updated. For more information see the [caveats](#caveats) section below.
#### Teardown the cluster
When you eventually `terraform destroy` the cluster, you should still run `kops delete cluster`, to remove the kops cluster specification and any dynamically created Kubernetes resources (ELBs or volumes). To do this, run:
@ -105,6 +107,12 @@ Ps: You don't have to `kops delete cluster` if you just want to recreate from sc
### Caveats
#### `kops rolling-update` might be needed after editing the cluster
Changes made with `kops edit` (like enabling RBAC and / or feature gates) will result in changes to the launch configuration of your cluster nodes. After a `terraform apply`, they won't be applied right away since terraform will not launch new instances as part of that.
In order to see your changes applied to the cluster you'll also need to run `kops rolling-update` after running `terraform apply`, this will ensure that all nodes changes have the desired settings configured with `kops edit`.
#### Workaround for Terraform <0.7
Before terraform version 0.7, there was a bug where it could not create AWS tags containing a dot. We recommend upgrading to version 0.7 or later, which will fix this bug. Please note that this issue only affects the volumes.