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

only wait for addons to be healthy if atleast 1 node instance exists #4629

Merged
merged 1 commit into from
Jan 14, 2022

Conversation

aclevername
Copy link
Contributor

Description

Closes #4607

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 🌟

@@ -42,7 +42,7 @@ func CreateAddonTasks(cfg *api.ClusterConfig, clusterProvider *eks.ClusterProvid
clusterProvider: clusterProvider,
forceAll: forceAll,
timeout: timeout,
wait: len(cfg.NodeGroups) > 0 || len(cfg.ManagedNodeGroups) > 0,
wait: cfg.HasNodes(),
Copy link
Contributor

Choose a reason for hiding this comment

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

Nice simplification

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.

When creating a cluster with 1 node group with no node, timeout waiting for coredns to become active.
2 participants