Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Allow setting set_values through helm_config for AWS load balancer controller addon #834

Merged
merged 2 commits into from
Aug 10, 2022

Conversation

bryantbiggs
Copy link
Contributor

@bryantbiggs bryantbiggs commented Aug 9, 2022

What does this PR do?

  • Allow setting set_values through helm_config for AWS load balancer controller addon
  • Changed the Fargate example (where the above change is demonstrated/tested) to deploy the sample app by default

Motivation

  • In order to set additional values, currently users would need to duplicate the values file which is not a great user experience. Instead, allowing users to pass in additional values through set_values allows for the default values file to stay as is as the minimum required values, and users can pass in any additional through the var.helm_config.set_values. The motivation for being able to set additional values - to able to set the pod disruption budget on the AWS LBC for better HA (discovered during testing for cluster upgrade guidance)
  • Deploying the sample app by default for the Fargate example is just to simplify things

More

  • Yes, I have tested the PR using my local account setup (Provide any test evidence report under Additional Notes)
  • Yes, I have added a new example under examples to support my PR
  • Yes, I have created another PR for add-ons under add-ons repo (if applicable)
  • Yes, I have updated the docs for this feature
  • Yes, I ran pre-commit run -a with this PR

Note: Not all the PRs required examples and docs except a new pattern or add-on added.

For Moderators

  • E2E Test successfully complete before merge?

Additional Notes

@bryantbiggs bryantbiggs temporarily deployed to EKS Blueprints Test August 9, 2022 19:19 Inactive
<<-EOT
clusterName: ${module.eks_blueprints.eks_cluster_id}
region: ${local.region}
vpcId: ${module.vpc.vpc_id}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we previously had to replicate the values file here in order to set the vpcId for running the AWS LBC on Fargate. now we can set just the additional values we need to provide to the AWS LBC addon

depends_on = [
kubernetes_namespace_v1.sample_app[0]
]
yaml_body = templatefile("sample_app.yaml", {
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

flattened to one multi-resource yaml file with templating so that we can map dependencies (by passing namespace from namespace resource)

@bryantbiggs bryantbiggs temporarily deployed to EKS Blueprints Test August 10, 2022 10:55 Inactive
@@ -6,7 +6,7 @@ locals {
name = local.name
chart = local.name
repository = "https://aws.github.io/eks-charts"
version = "1.4.2"
version = "1.4.3"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1.4.4 is out today

Copy link
Contributor

@Zvikan Zvikan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, we should consider applying the same change to all the other addons following the same motivation mentioned here.

@bryantbiggs bryantbiggs merged commit 96a1427 into main Aug 10, 2022
@bryantbiggs bryantbiggs deleted the feat/aws-lbc-set-values branch August 10, 2022 13:50
allamand pushed a commit to allamand/terraform-aws-eks-blueprints that referenced this pull request Dec 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants