Howto: run multiple clusters.

[mcameron]

I'm looking for confirmation that tack can be used to run multiple clusters in one AWS account, in such a way that one cluster can be cleaned, leaving the other cluster untouched.

This does require an amount of terraform state file handling and I plan to use terragrunt for that. Happy to provide a PR, if that's of use.

Mainly I want to be confident that a make clean is safe and that nothing is shared between the two clusters spun up with different names (security groups for example).

[mcameron]

I probably should also mention that I'm a big fan, and have had better results with Tack than I've had with Kops or Kube-aws so far, so thank you.

[yagonobre]

I run multiple clusters in one AWS account, using tack but I modified tack for storage terraform state in s3. I think that terragrunt can work fine.

[lexhung]

Hi all,

I created a modified version of tack where we can easily create multiple clusters.

It is same with normal tack except you have to provide a cluster config before running make.

E.g. ENV=prod make all or (make all ENV=test)

Generated files of each cluster will be put under a sub folder of ./build

E.g. build/name.toplevel.domain

I can send a pull request if we find it useful.

---

https://github.com/lexhung/tack/blob/master/Makefile
https://github.com/lexhung/tack

[mcameron]

Thanks for the links @lexhung.

@lexhung the diff here is quite big: master...lexhung:master

Are all those changes required for running multiple clusters in one account, or is it just 8a83ab9 and 3b9a34f?

[cemo]

For what it's worth, Terraform will provide environments in 0.9. This is still in beta and in 2 months I expect a release.

[owenmorgan]

@cemo do you have documentation on environments?

[cemo]

@owenmorgan check this PR and related files:

https://github.com/hashicorp/terraform/pull/12366/files

[lexhung]

@mcameron In order to enable multi-cluster, the changes here are:

• putting the paths into variables (so I can better track/switch the filepaths of each cluster)
• using a single source of terraform output (see .tfstate task in makefiles/terraform.mk) so we don't have to run terraform output everytime we need those values.
• plug directory variables into terraform config ("build-dir", "dir-tmp", "dir-ssl", "dir-keypair")
• modify the terraform commands to use new configuration, states, plan locations.
• a few tweaks for my particular use case (e.g. disable busybox-test, VPC rule warning, ...) which I can revert for the pull request.

[cemo]

@owenmorgan Terraform 0.9 is released.

[owenmorgan]

Thanks