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: Add support for EKS addon data version selection of most_recent (true/false) #1048

Merged
merged 3 commits into from
Oct 13, 2022

Conversation

bryantbiggs
Copy link
Contributor

What does this PR do?

  • Add support for EKS addon data version selection of most_recent (true/false)
  • All EKS addons have been updated to align their default configurations. This includes setting resolve_conflicts as "OVERWRITE" as the default

Motivation

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 require a new example and/or doc page. In general:

  • Use an existing example when possible to demonstrate a new addons usage
  • A new docs page under docs/add-ons/* is required for new a new addon

For Moderators

  • E2E Test successfully complete before merge?

Additional Notes

@bryantbiggs bryantbiggs temporarily deployed to EKS Blueprints Test October 11, 2022 18:32 Inactive
@@ -33,6 +31,8 @@ repos:
- '--args=--only=terraform_required_providers'
- '--args=--only=terraform_standard_module_structure'
- '--args=--only=terraform_workspace_remote'
- id: terraform_validate
Copy link
Contributor Author

Choose a reason for hiding this comment

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

just moved lower in the checks since it takes the longest - the shortest checks will return first before the longer checks

module "eks_blueprints_kubernetes_addons" {
# Essential inputs are not shown for brevity

enable_amazon_eks_coredns = true
amazon_eks_coredns_config = {
addon_version = data.aws_eks_addon_version.default["coredns"].version
resolve_conflicts = "OVERWRITE"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

removing defaults and showing whats unique

@askulkarni2 askulkarni2 temporarily deployed to EKS Blueprints Test October 12, 2022 22:38 Inactive
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!

@bryantbiggs bryantbiggs merged commit 55adfc0 into main Oct 13, 2022
@bryantbiggs bryantbiggs deleted the feat/managed-addon-versions branch October 13, 2022 00:31
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.

EKS Addons should support upgrading version aligned with cluster version
2 participants