Skip to content

Namespace non existent should be handled #2180

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.

Sign up for GitHub

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

Jump to bottom
Closed
jeffmaury opened this issue Jun 25, 2021 · 4 comments · Fixed by #2837
Closed

Namespace non existent should be handled #2180

jeffmaury opened this issue Jun 25, 2021 · 4 comments · Fixed by #2837
Assignees
@datho7561
Labels
kind/enhancement New feature or request priority/major
Milestone
1.3.0

Comments

@jeffmaury
Copy link
Member

If the current context is using a non existent namespace on the cluster, the Application Explorer is empty. We should handle this case:

  • take the first available namespace
  • if no namespaces are available display a link to create a new namespace/project
@dgolovin dgolovin added kind/enhancement New feature or request priority/major labels Jun 25, 2021
@dgolovin dgolovin added this to the v0.2.8 milestone Jun 25, 2021
@dgolovin dgolovin self-assigned this Jul 1, 2021
@dgolovin dgolovin modified the milestones: v0.2.8, v0.2.9, v0.2.10 Jul 3, 2021
@dgolovin dgolovin modified the milestones: v0.2.10, v0.2.11 Aug 18, 2021
@mohitsuman mohitsuman modified the milestones: 1.2.0, 1.1.0 Nov 13, 2022
@mohitsuman
Copy link
Collaborator

@dgolovin We need to test if this scenario exists for the current workflow.

@mohitsuman mohitsuman modified the milestones: 1.1.0, 1.2.0 Nov 23, 2022
@mohitsuman mohitsuman modified the milestones: 1.2.0, 1.3.0 Jan 4, 2023
@datho7561
Copy link
Contributor

I am looking to help out with OpenShift Toolkit. Do you think this would be a good issue to start with?

@mohitsuman mohitsuman assigned datho7561 and unassigned dgolovin Mar 23, 2023
@mohitsuman mohitsuman modified the milestones: 1.3.0, 1.4.0 Mar 23, 2023
@mohitsuman mohitsuman moved this to 📋 Backlog in IDE Cloudaptors Apr 5, 2023
@datho7561
Copy link
Contributor

I can recreate this issue by setting the context to a non existing namespace using kubectl config set-context.

When using a non-existant namespace, all the UI elements are greyed out, so I can't change namespaces using OpenShift Toolkit.

@datho7561
Copy link
Contributor

Ugh now I can't do anything at all with the extension :(

@datho7561 datho7561 mentioned this issue Apr 17, 2023
Merged
datho7561 added a commit to datho7561/vscode-openshift-tools that referenced this issue Apr 18, 2023
@datho7561
Switch to first available namespace
5618f79 
When the currently configured namespace doesn't exist, switch to the
first available namespace.

Closes redhat-developer#2180

Signed-off-by: David Thompson <[email protected]>
@datho7561 datho7561 moved this from 📋 Backlog to 👀 In review in IDE Cloudaptors Apr 19, 2023
rgrunber pushed a commit that referenced this issue Apr 25, 2023
@datho7561 @rgrunber
Switch to first available namespace
571fbc8 
When the currently configured namespace doesn't exist, switch to the
first available namespace.

Closes #2180

Signed-off-by: David Thompson <[email protected]>
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in IDE Cloudaptors Apr 25, 2023
@rgrunber rgrunber modified the milestones: 1.4.0, 1.3.0 Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@datho7561 datho7561

Labels
kind/enhancement New feature or request priority/major
Projects
IDE Cloudaptors
Archived in project
Milestone
1.3.0
Development

Successfully merging a pull request may close this issue.

Switch to first available namespace datho7561/vscode-openshift-tools
5 participants
@dgolovin @jeffmaury @rgrunber @mohitsuman @datho7561