Skip to content
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

Dashboard does not remember namespace after adding resource. #4282

Closed
resuls opened this issue Sep 12, 2019 · 2 comments · Fixed by #5033
Closed

Dashboard does not remember namespace after adding resource. #4282

resuls opened this issue Sep 12, 2019 · 2 comments · Fixed by #5033
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@resuls
Copy link

resuls commented Sep 12, 2019

Issue details

Dashboard does not remember last selected namespace after adding a resource.

Environment

Dashboard version: v2.0.0-beta3+0.g677aff93
Kubernetes version: v1.15.0
Operating system: Debian
Node.js version: n/a
Go version: n/a

Steps to reproduce

Select a namespace other than the default.
Build a simple YAML of any resource (example a secret), upload it through the YAML upload dialog.

Observed result

After the successful creation of a resource, the namespace will be set as default again.

Expected result

It should remember the last selected namespace after creation.

@resuls resuls added the kind/bug Categorizes issue or PR as related to a bug. label Sep 12, 2019
@floreks floreks added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Sep 19, 2019
@floreks floreks added this to the v2.0.0-rc1 milestone Sep 19, 2019
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 18, 2019
@maciaszczykm maciaszczykm removed this from the v2.0.0-rc1 milestone Jan 9, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 8, 2020
@floreks floreks added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Feb 8, 2020
@floreks floreks linked a pull request Mar 26, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
5 participants