fix: handle kubernetes connection in startProvider function#8629
Merged
Conversation
Signed-off-by: lstocchi <lstocchi@redhat.com>
Contributor
Author
|
@dgolovin @jeffmaury -> for crc-org/crc-extension#247 in crc |
benoitf
approved these changes
Aug 29, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What does this PR do?
This PR enhances the startProvider function to check for kubernetes connections as well. This would fix an issue faced on crc
Screenshot / video of UI
N/A
What issues does this PR fix or reference?
it resolves #8514
How to test this PR?
initialize and startfrom the dashboard.