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 UI: show all user facing resources #136

Closed
11 of 14 tasks
bryk opened this issue Oct 25, 2016 · 6 comments
Closed
11 of 14 tasks

Dashboard UI: show all user facing resources #136

bryk opened this issue Oct 25, 2016 · 6 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/ui Categorizes an issue or PR as relevant to SIG UI.

Comments

@bryk
Copy link

bryk commented Oct 25, 2016

Description

User story: As a user I want to be able to access my cluster using only UI, only CLI or any mix of CLI and UI interactions. I want to see my entire application architecture through the UI.

Goals: The Dashboard UI shows all user facing resources and allows for CRUD operations on them. We define "user facing resources" as all Kubernetes resources that cluster admin or cluster users may want to interact with during their daily routine. In the view, the UI should show resource specification, status and all metadata. It should also link to all related resources, e.g., creator of a pod, or Deployment's Replica Sets. CRUD should be done as generic YAML/JSON editors that are equivalent to kubectl edit.

Progress Tracker

We moved this feature from kubernetes/dashboard#961 to this issue. Alpha is already implemented, so was not tracked here. Development artifacts are linked here for reference.

  • Alpha
  • Beta
    • Testing is sufficient for beta
    • All resources are properly handled in the UI
    • User docs with tutorials
      • Updated walkthrough / tutorial in the docs repo: kubernetes/kubernetes.github.io
      • cc @kubernetes/docs on docs PR
      • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off
  • Stable
    • Soak, load testing
    • detailed user docs and examples
      • cc @kubernetes/docs
      • cc @kubernetes/feature-reviewers on this issue to get approval before checking this off

FEATURE_STATUS: BETA

More advice:

Design

  • Once you get LGTM from a @kubernetes/feature-reviewers member, you can check this checkbox, and the reviewer will apply the "design-complete" label.

Docs

  • Write user docs and get them merged in.
  • User docs go into http://github.com/kubernetes/kubernetes.github.io.
  • When the feature has user docs, please add a comment mentioning @kubernetes/docs.
  • When you get LGTM, you can check this checkbox, and the reviewer will apply the "docs-complete" label.
@bryk bryk added sig/ui Categorizes an issue or PR as relevant to SIG UI. stable-in-1.5 labels Oct 25, 2016
@idvoretskyi idvoretskyi added this to the v1.5 milestone Oct 26, 2016
@idvoretskyi
Copy link
Member

@bryk can you provide the actual status of the feature?

@bryk
Copy link
Author

bryk commented Nov 3, 2016

Currently in late beta. We display all except two user facing resources. Now we continue work on showing more resource properties better.

Docs and user guides are poor, though.

bryk added a commit to kubernetes/website that referenced this issue Nov 25, 2016
@idvoretskyi idvoretskyi modified the milestones: v1.6, v1.5 Dec 13, 2016
@idvoretskyi idvoretskyi modified the milestones: next-milestone, v1.6 Jan 12, 2017
@idvoretskyi
Copy link
Member

@bryk are you expecting this feature to be present in 1.6 (as a stable, after beta)?

@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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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 Jan 2, 2018
@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
/remove-lifecycle stale

@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 7, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

ingvagabund pushed a commit to ingvagabund/enhancements that referenced this issue Apr 2, 2020
…ts-builds-and-imageregistryimport

Using node pull credentials during builds, image stream imports and pull-through
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/ui Categorizes an issue or PR as relevant to SIG UI.
Projects
None yet
Development

No branches or pull requests

4 participants