prow-build-cluster: deploy cluster-autoscaler, metrics-server, and AWS Secrets Manager integration #4873
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on requirements stated in #4686, this PR ensures we deploy the following components in
prow-build-cluster
:All components are fully-managed by Terraform. Kubernetes YAML manifests were converted to Terraform (
.tf
) files usingtfk8s
and deployed using thehashicorp/kubernetes
provider. Helm charts are reconciled using thehashicorp/helm
provider.IRSA (IAM role for Service Account) for Secrets Manager is commented and provided as a reference. It's supposed to uncommented and updated based on what we want to use the Secrets Manager for.
The reason for going with Terraform for everything is to:
terraform apply
invocationThis change is already reconciled. Additionally, the all three components were tested and are working well.
/assign @ameukam @upodroid