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

fix: Karpenter enable_spot_termination = false should not result in an error #2907

Conversation

nikoshet
Copy link
Contributor

@nikoshet nikoshet commented Feb 6, 2024

Description

This change adds a condition on the statement with id AllowInterruptionQueueActions that checks enable_spot_termination value, since, if the variable is false, the aws_sqs_queue resource will not be created.

Motivation and Context

Resolves: #2906

Breaking Changes

No breaking changes.

How Has This Been Tested?

  • I have updated at least one of the examples/* to demonstrate and validate my change(s)
  • I have tested and validated these changes using one or more of the provided examples/* projects
  • I have executed pre-commit run -a on my pull request

@bryantbiggs bryantbiggs changed the title fix: Add condition for statement if enable_spot_termination is true fix: Karpenter enable_spot_termination = false should not result in an error Feb 8, 2024
@bryantbiggs bryantbiggs merged commit 671fc6e into terraform-aws-modules:master Feb 8, 2024
18 checks passed
antonbabenko pushed a commit that referenced this pull request Feb 8, 2024
### [20.2.1](v20.2.0...v20.2.1) (2024-02-08)

### Bug Fixes

* Karpenter `enable_spot_termination = false` should not result in an error ([#2907](#2907)) ([671fc6e](671fc6e))
@antonbabenko
Copy link
Member

This PR is included in version 20.2.1 🎉

@nikoshet nikoshet deleted the feat/allow-disabled-aws_sqs_queue branch February 8, 2024 11:00
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Karpenter] TF apply fails with eks module v20 when enable_spot_termination=false and create_iam_role=true
3 participants