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

Do not create nodegroup if --fargate is set and --managed is not provided #4135

Merged
merged 1 commit into from Aug 27, 2021

Conversation

cPu1
Copy link
Collaborator

@cPu1 cPu1 commented Aug 25, 2021

Description

Closes #4111

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 added the kind/bug label Aug 25, 2021
@cPu1 cPu1 changed the title Do not create a nodegroup if --fargate is set and --managed is not provided Do not create nodegroup if --fargate is set and --managed is not provided Aug 25, 2021
@cPu1
Copy link
Collaborator Author

cPu1 commented Aug 25, 2021

I'm running the integration tests on this branch before merging.

@cPu1
Copy link
Collaborator Author

cPu1 commented Aug 27, 2021

Integration tests failed but it was due to exceeding resource usage. I'm proceeding with merging.

@cPu1 cPu1 merged commit 1a86963 into eksctl-io:main Aug 27, 2021
@cPu1 cPu1 deleted the fargate-no-nodegroups branch August 27, 2021 08:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The --fargate flag now creates two worker nodes (while in the past it did not)
2 participants