Dustin
c63c4d9e8c
dustin/dynk8s-provisioner/pipeline/head This commit looks good
Details
If a Jenkins job runs for a while, Kubernetes may schedule other Pods on it eventually. If a long-running Pod gets assigned to the ephemeral node, the Cluster Autoscaler won't be able to scale down the ASG. To prevent this, we apply a taint to the node so normal Pods will not get assigned to it. We have to apply the corresponding toleration to Pods for Jenkins jobs. |
||
|---|---|---|
| .. | ||
| .gitattributes | ||
| .gitignore | ||
| .terraform.lock.hcl | ||
| README.md | ||
| asg.tf | ||
| eventbridge.tf | ||
| iam-policy.json | ||
| main.tf | ||
| sns.tf | ||
| terraform.tfstate | ||
| userdata.yml | ||
| variables.tf | ||
README.md
Configuring AWS Using Terraform
Prerequisites
The IAM user or role that runs Terraform must have the appropriate permissions.
The iam-policy.json file defines a policy that will allow the Terraform to
manage all of the necessary resources. Before running Terraform, create an IAM
policy and assign it to a user, group, or role. Be sure to replace the AWS
account ID in the various target resource names.
To use an IAM role, set the iam_role Terraform variable when executing
terraform plan/terraform apply.
Create Resources
Terraform will create all resources automatically:
terraform apply