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
Create UI roadmap #8270
Labels
area/kubectl
area/ui
area/usability
kind/documentation
Categorizes issue or PR as related to documentation.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Comments
bgrant0607
added
area/usability
area/ui
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
labels
May 14, 2015
@bgrant0607 we've got a organization for the various UI components that is currently living at: https://github.com/kubernetes-ui in order to share things with the team at RedHat, etc. |
bgrant0607
added
kind/documentation
Categorizes issue or PR as related to documentation.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
area/kubectl
and removed
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
labels
Jul 1, 2015
cc @mgannholm |
cc @janetkuo |
Link to applications: #6908 |
bgrant0607
added
team/ux
and removed
sig/api-machinery
Categorizes an issue or PR as relevant to SIG API Machinery.
labels
Aug 5, 2015
cc @bryk |
Copied to kubernetes/dashboard#21 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/kubectl
area/ui
area/usability
kind/documentation
Categorizes issue or PR as related to documentation.
priority/backlog
Higher priority than priority/awaiting-more-evidence.
Going forward, what do we want out of the UI? We need a roadmap so that people know how to contribute.
This was discussed at the Kubernetes contributors meeting in December.
First of all, visualization/dashboard is more important than actuation. The CLI (kubectl) is expected to be the main tool for controlling the system and applications running on it. Table-friendly views should also be incorporated into kubectl, not just a GUI. I want to ensure that we maintain a common look and feel and functionality with kubectl for analogous table views and use cases -- the primary use cases and essential information are identical. That's not to say it shouldn't support actuation, but that creates additional issues, such as SSO auth.
With respect to visualization/dashboards, we need views that are customized to the most common use cases:
Some functionality is probably lacking in order to support all these views at the moment (e.g., stats collection).
Presentation guidelines:
Come up with recommended semantic labels/annotation keys and meanings:
Other issues:
Finally, there are others building UIs. We've discussed building the UI such that pieces can be reused with different chrome, etc.
cc @lavalamp @jackgr @smarterclayton
The text was updated successfully, but these errors were encountered: