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

No architecture diagram in "Kubernetes Design and Architecture" #767

Closed
tauqeerhassan opened this issue Jun 27, 2017 · 12 comments
Closed

No architecture diagram in "Kubernetes Design and Architecture" #767

tauqeerhassan opened this issue Jun 27, 2017 · 12 comments
Labels
area/developer-guide Issues or PRs related to the developer guide lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture.

Comments

@tauqeerhassan
Copy link

Amazed to see no diagrams under a section named Architecture. It become easy to understand the whole thing if it has some logical or actual diagrammatic representation.

@cblecker
Copy link
Member

We're in the process of forming a formalized sig-architecture to oversee this kind of thing. The thread about it is here, and there is a number of good resources including a presentation and diagrams.

@bgrant0607
Copy link
Member

One possible source is this slide:
https://docs.google.com/presentation/d/1oPZ4rznkBe86O4rPwD2CWgqgMuaSXguIBHIE7Y0TKVc/edit#slide=id.g21b1f16809_1_79

cc @kubernetes/sig-architecture-bugs

@bgrant0607 bgrant0607 added the sig/architecture Categorizes an issue or PR as relevant to SIG Architecture. label Jul 24, 2017
@xiangpengzhao
Copy link
Contributor

@bgrant0607
Copy link
Member

@xiangpengzhao I removed links to that picture because it has numerous problems. For instance, I'd like to remove mention of cadvisor, which isn't a separate component. There is also no "scheduling actuator", the proxy is misleading, it doesn't mention the apiserver, it doesn't mention CRI and other more recent developments, etc.

And it's not very attractive.

@xiangpengzhao
Copy link
Contributor

@bgrant0607 yeah :)

@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 3, 2018
@nikhita
Copy link
Member

nikhita commented Jan 16, 2018

/remove-lifecycle stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 16, 2018
@nikhita
Copy link
Member

nikhita commented May 3, 2019

/area developer-guide

@k8s-ci-robot k8s-ci-robot added the area/developer-guide Issues or PRs related to the developer guide label May 3, 2019
@vishakhanihore
Copy link
Contributor

vishakhanihore commented Dec 19, 2019

@cblecker @nikhita I found this architecture diagram in the K8 Website, Will the following diagram work for same?
Screenshot 2019-12-19 at 7 03 56 PM

Or

Screenshot 2019-12-19 at 7 05 14 PM

@mrbobbytables
Copy link
Member

Is this still relevant? It's been open and frozen for some time now.
I'm going to mark it as rotten for now, if it should be left open please update or re-freeze it 👍

/remove-lifecycle frozen
/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/frozen Indicates that an issue or PR should not be auto-closed due to staleness. labels May 18, 2020
@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

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

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

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

danehans pushed a commit to danehans/community that referenced this issue Jul 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/developer-guide Issues or PRs related to the developer guide lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/architecture Categorizes an issue or PR as relevant to SIG Architecture.
Projects
None yet
Development

No branches or pull requests

9 participants