Open miyadav opened 2 years ago
@miyadav: The label triage/accepted
cannot be applied. Only GitHub organization members can add the label.
cc @divya-mohan0209 , @sftim .
Page: https://kubernetes.io/docs/concepts/overview/components/ /kind feature /language en
/area web-development
/triage accepted
/retitle Make cluster diagram(s) more comprehensible
Hey, @sftim can I work on this? Please correct me, if I am wrong. This needs some hover effects showing some details about the icon.
I'm open to hearing about different ideas about ways to improve things. Hover effects are just one option - and won't work on touchscreen devices such as phones and tablets.
Another option is to drop the icons and use words instead; in fact, that's what an older version of that diagram did. Or we could use words plus icons, using those symbols more like badges. Or something else I didn't think of.
My preference is KEEP IT SIMPLE. Just use boxes, lines, arrows and words. IMHO new users can grasp architecture components faster and contributors can create/modify diagrams much easier. Here is a "hack-ish" example contained in the Mermaid live editor of how you could to do this using open-source Mermaid:
Partial example of K8s components diagram using Mermaid
You can click on a node to point to more detailed info. Try it with etcd node in the example. If we think some iconography helps, Mermaid can use fontawesome.
Check out the Diagram Guide for more info on Mermaid. This approach subscribes to the Diagrams-as-code paradigm.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
Hey @miyadav, I had created a prototype of diagram. Please take look & let me know for any changes. Or should raise a PR.
Regards.
Thanks @devarsh10 for looking into it , but the flowchart is conceptually exactly same as the existing diagram so not adding much value , may be you can make a PR to add text-hover / hyperlink on existing diagram . may be @sftim can give you better feedback .
Thanks for your reply. I'll try to improve the existing one. And my prototype consists of hyperlinks.[Hope you noticed].
Using text labels is helpful. I suggest that each person who's making a proposal opens a pull request. You can start with an empty commit and use the PR comments to run a discussion.
That way, we can have conversations between authors and other contributors, with each conversation happening separately (mixing them up may be confusing!)
Okay. So @sftim, may I raise a PR? By adding my prototype's link.
Anyone who follows the code of conduct - basically, be nice to people - is welcome to contribute. You will need to sign the CLA as well - you can do that as an individual or through your employer, whichever is more appropriate.
Hey all, I raised a PR #39389. Please take a look into it. And let me know for some changes to be made.
Regards.
This issue has not been updated in over 1 year, and should be re-triaged.
You can:
/triage accepted
(org members only)/close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/triage accepted
not removing stale marker
I'd be happy to see a bigger change to the diagram, eg adding a tooltip for each component, or letting you click on (eg) the k-c-m icon to see details of the component. There is room to improve.
This smaller change feels like it's not enough of an improvement though.
_Originally posted by @sftim in https://github.com/kubernetes/website/pull/34841#discussion_r916606830_