2.5 KiB
2.5 KiB
Kubernetes & Multiple Environments
Kubernetes Demo
terraform init
Multiple Environments
If we wanted to take any of the demos we have ran through but wanted to now have specific production, staging and development environments looking exactly the same and leveraging this code there are two approaches to achieve this with Terraform
-
terraform workspaces- multiple named sections within a single backend -
file structure - Directory layout provides separation, modules provide reuse.
Each of the above do have their pros and cons though.
terraform workspaces
Pros
- Easy to get started
- Convenient terraform.workspace expression
- Minimises code duplication
Cons
- Prone to human error (we were trying to eliminate this by using TF)
- State stored within the same backend
- Codebase doesnt unambiguously show deployment configurations.
File Structure
Pros
- Isolation of backends
- improved security
- decreased potential for human error
- Codebase fully represents deployed state
Cons
- Multiple terraform apply required to provision environments
- More code duplication, but can be minimised with modules.
Resources
I have listed a lot of resources down below and I think this topic has been covered so many times out there, If you have additional resources be sure to raise a PR with your resources and I will be happy to review and add them to the list.
- What is Infrastructure as Code? Difference of Infrastructure as Code Tools
- Terraform Tutorial | Terraform Course Overview 2021
- Terraform explained in 15 mins | Terraform Tutorial for Beginners
- Terraform Course - From BEGINNER to PRO!
- HashiCorp Terraform Associate Certification Course
- Terraform Full Course for Beginners
- KodeKloud - Terraform for DevOps Beginners + Labs: Complete Step by Step Guide!
- Terraform Simple Projects
- Terraform Tutorial - The Best Project Ideas
- Awesome Terraform
See you on Day 57