generated from redhat-developer/new-project-template
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Extension requires me to continually create new contexts #65
Labels
kind/enhancement ✨
New feature or request
Comments
See #20 (comment) |
Having a default (non-conflicting) name as per #20 would be great and help with usability, but wouldn't solve this problem where I continually need to create new instances and delete old ones. |
For now it is manual process. One have to recreate context when token is expired. Going to improve it next sprints. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I started Podman Desktop, and the sandbox instance I was using yesterday has 'unknown' status. Ok, no problem, it must just be logged out. But to log in again I had to:
oc login
command... which created a new context instead of using the one I had created yesterday. I can set this context inside of Podman Desktop using the system tray, but my Sandbox instance still says 'unknown'. I can't edit the instance to change the context; I can't create a new instance with the new context b/c it already exists. The only way to show the sandbox connection as running again is to create a new instance with a third context.
The text was updated successfully, but these errors were encountered: