fix: error clearly if there are no nodes on the Kubernetes cluster #1553
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
leoporoli
approved these changes
Oct 17, 2023
github-merge-queue bot
pushed a commit
that referenced
this pull request
Oct 17, 2023
🤖 I have created a release *beep* *boop* --- ## [0.84.8](0.84.7...0.84.8) (2023-10-17) ### Features * kurtosis package init command ([#1547](#1547)) ([6411c8f](6411c8f)) ### Bug Fixes * correct the link to kurtosis upgrade docs ([#1574](#1574)) ([11d1dba](11d1dba)) * error clearly if there are no nodes on the Kubernetes cluster ([#1553](#1553)) ([77f9ad4](77f9ad4)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: kurtosisbot <kurtosisbot@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
An AWS EKS cluster starts with no nodes which is quite confusing for the user if the engine doesn't start. This checks if there are any nodes and otherwise tells the user there aren't
Is this change user facing?
YES
References (if applicable):
#1507