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(cluster-autoscaler): allow user to upgrade cluster-autoscaler #715

Conversation

chubchubsancho
Copy link
Contributor

Previously image.tag was set through set_values
Due to this we were unable to upgrade cluster-autoscaler

  • redifine cluster-autoscaler image.tag on values.yaml
  • remove set_values

What does this PR do?

Define default value for cluster-autoscaler based on cluster version and let user override this value

Motivation

Resolv #714

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

Copy link
Contributor

@vara-bonthu vara-bonthu left a comment

Choose a reason for hiding this comment

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

Thanks for the fix @chubchubsancho . I agree with this approach 👍🏼

@@ -19,6 +19,7 @@ module "helm_addon" {
values = [templatefile("${path.module}/values.yaml", {
aws_region = var.addon_context.aws_region_name,
eks_cluster_id = var.addon_context.eks_cluster_id
Copy link
Contributor

Choose a reason for hiding this comment

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

Just noticed. You are missing a , at end of this line.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

nice catch i fix this

Copy link
Contributor

Choose a reason for hiding this comment

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

I dont think you need a , in values template but the line number 20 has got one. That can be removed instead

Copy link
Contributor Author

Choose a reason for hiding this comment

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

you're right , is not needed here just removed it

@chubchubsancho chubchubsancho force-pushed the feat/cluster-autoscaler/ability-to-specify-image-tag branch from a9c9119 to e3e840f Compare June 30, 2022 13:59
Previously `image.tag` was set through `set_values`
Due to this we were unable to upgrade cluster-autoscaler
* redifine cluster-autoscaler image.tag on `values.yaml`
* remove `set_values`
@chubchubsancho chubchubsancho force-pushed the feat/cluster-autoscaler/ability-to-specify-image-tag branch from e3e840f to 3855efe Compare June 30, 2022 14:10
@chubchubsancho chubchubsancho temporarily deployed to EKS Blueprints Test June 30, 2022 14:10 Inactive
Copy link
Contributor

@vara-bonthu vara-bonthu left a comment

Choose a reason for hiding this comment

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

LGTM 👍🏼

Copy link
Contributor

@askulkarni2 askulkarni2 left a comment

Choose a reason for hiding this comment

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

LGTM!

@askulkarni2 askulkarni2 merged commit 3c2ba25 into aws-ia:main Jun 30, 2022
@chubchubsancho chubchubsancho deleted the feat/cluster-autoscaler/ability-to-specify-image-tag branch June 30, 2022 19:07
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