Create a backend.tf file from backend.tf.example and fill the missing values.
cp backend.tf.example backend.tf
Create a config file for your environment by copying config/env.tfvars.example and fill the missing values
cp config/env.tfvars.example <env_name>.tfvars
Execute terraform init, if successful your output should look like this
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
Execute terraform plan -var-file=config/env.tfvars
Plan: 27 to add, 1 to change, 0 to destroy.
------------------------------------------------------------------------
Note: You didn't specify an "-out" parameter to save this plan, so Terraform
can't guarantee that exactly these actions will be performed if
"terraform apply" is subsequently run.
Releasing state lock. This may take a few moments...
Execute terraform apply -var-file=config/env.tfvars and answer yes when prompted.
Apply complete! Resources: 27 added, 0 changed, 0 destroyed.
Releasing state lock. This may take a few moments...
Once terraform is done you can check the state of the cluster with:
export KOPS_STATE_STORE=s3://<kops_state_bucket> # Get this values from config/<env_name>.tfvars
kops export kubecfg --admin --name <name>.<hosted_zone>
kops validate cluster
After kops reports your cluster as valid you can start running kubectl commands:
Using cluster from kubectl context: <name>.<hosted_zone>
Validating cluster <name>.<hosted_zone>
INSTANCE GROUPS
NAME ROLE MACHINETYPE MIN MAX SUBNETS
agent Node t3.medium 1 2 PrivateSubnet-0,PrivateSubnet-1,PrivateSubnet-2
master-us-west-2a Master t3.medium 1 1 PrivateSubnet-0
master-us-west-2b Master t3.medium 1 1 PrivateSubnet-1
master-us-west-2c Master t3.medium 1 1 PrivateSubnet-2
NODE STATUS
NAME ROLE READY
ip-10-2-2-68.us-west-2.compute.internal master True
ip-10-2-3-217.us-west-2.compute.internal master True
ip-10-2-3-218.us-west-2.compute.internal node True
ip-10-2-4-251.us-west-2.compute.internal master True
Your cluster <name>.<hosted_zone> is ready
For example kubectl get nodes should output something like this:
NAME STATUS ROLES AGE VERSION
ip-10-2-2-68.us-west-2.compute.internal Ready master 5m v1.11.9
ip-10-2-3-217.us-west-2.compute.internal Ready master 5m v1.11.9
ip-10-2-3-218.us-west-2.compute.internal Ready node 4m v1.11.9
ip-10-2-4-251.us-west-2.compute.internal Ready master 5m v1.11.9
To destroy the environment simply run terraform destroy -var-file=config/env.tfvars and answer yes when prompted.
To manually destroy the cluster run kops delete cluster <name>.<hosted_zone> --yes
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent