Show more user feedback when Zarf cannot connect to a cluster #1541
Comments
|
Labeling this as a bug because the 30 second timeout we are setting is getting ignored. |
5 tasks
Racer159
added a commit
that referenced
this issue
Apr 18, 2023
…ushes (#1590) ## Description This PR creates a tunnel per image push (making it easier to implement concurrency - may do that in this PR if we can confirm that issues are mitigated) moves the CRC from the image name to the tag and changes the UI to use a progressbar instead of a spinner for better user feedback. ## Related Issue Relates to #1568 , #1433, #1218, #1364 This also will make #1594 slightly easier. (See aws/containers-roadmap#853) Fixes: #1541 ## Type of change - [X] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Other (security config, docs update, etc) ## Checklist before merging - [X] Test, docs, adr added or updated as needed - [X] [Contributor Guide Steps](https://github.com/defenseunicorns/zarf/blob/main/CONTRIBUTING.md#developer-workflow) followed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
When Zarf cannot connect to a cluster it will stall after "Copying 1 files" for quite some time.
Describe the solution you'd like
We should show more clearly that we are trying to connect to a cluster but are unable to do so. We should also likely lower the timeout for receiving a response.
Describe alternatives you've considered
None
Additional context
This is something that has impacted users with misconfigured
~/./kube/configfiles in the real world.The text was updated successfully, but these errors were encountered: