Dashboard UI: show all user facing resources

[bryk]

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
  • Design Approval
    • Design Proposal. This goes under docs/proposals. Doing a proposal as a PR allows line-by-line commenting from community, and creates the basis for later design documentation. Paste link to merged design proposal here: Design doc for next version of user experience of the UI dashboard#589
    • Decide which repo this feature's code will be checked into. Not everything needs to land in the core kubernetes repo. https://github.com/kubernetes/dashboard
    • Identify shepherd (your SIG lead and/or kubernetes-pm@googlegroups.com will be able to help you). My Shepherd is: @bryk @pwittrock
    • Identify secondary/backup contact point. My Secondary Contact Point is: @rf232
• 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.

[idvoretskyi]

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

[bryk]

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.

[idvoretskyi]

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

[fejta-bot]

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

[fejta-bot]

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

[fejta-bot]

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