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.

Sign up for GitHub

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

Jump to bottom

Improve error message when Fargate is unsupported in an AZ #5875

Merged
merged 2 commits into from
Nov 7, 2022
Merged

Improve error message when Fargate is unsupported in an AZ #5875

merged 2 commits into from
Nov 7, 2022

Conversation

cPu1
Copy link
Contributor

@cPu1 cPu1 commented Nov 7, 2022 •
edited
Loading

Description

Closes #5677

Checklist

  • Added tests that cover your change (if possible)
  • Added/modified documentation as required (such as the README.md, or the userdocs directory)
  • Manually tested
  • Made sure the title of the PR is a good description that can go into the release notes
  • (Core team) Added labels for change area (e.g. area/nodegroup) and kind (e.g. kind/improvement)

BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯

  • Backfilled missing tests for code in same general area 🎉
  • Refactored something and made the world a better place 🌟

@cPu1 cPu1 mentioned this pull request Nov 7, 2022
Closed
@cPu1 cPu1 enabled auto-merge (squash) November 7, 2022 15:42
@cPu1 cPu1 merged commit 9eac854 into eksctl-io:main Nov 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@TiberiuGC TiberiuGC TiberiuGC approved these changes

Assignees
No one assigned
Labels
area/fargate kind/improvement
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[Bug] eksctl failed to create fargate profile in YUL when --fargate is included
2 participants
@cPu1 @TiberiuGC