github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-26 05:03:09 +00:00
Code Issues Projects Releases Wiki Activity

Link to architecture diagram

Browse Source
This commit is contained in:
Daniel Smith 2014-07-18 23:29:58 -07:00
parent d1de579070
commit 06c55d142e
1 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
DESIGN.md
View File

@ -38,6 +38,12 @@ A single Kubernetes cluster is not intended to span multiple availability zones.
Kubernetes is not currently suitable for use by multiple users -- see [Cluster Security](#cluster-security), below. Kubernetes is not currently suitable for use by multiple users -- see [Cluster Security](#cluster-security), below.
### Cluster Architecture
A running Kubernetes cluster contains node agents (kubelet) and master components (APIs, scheduler, etc), on top of a distributed storage solution. This diagram shows our desired eventual state, though we're still working on a few things, like making kubelet itself (all our components, really) run within docker, and making the scheduler 100% pluggable.
![Architecture Diagram](/docs/architecture.png?raw=true "Architecture overview")
## Key Concepts ## Key Concepts
While Docker itself works with individual containers, Kubernetes provides higher-level organizational constructs in support of common cluster-level usage patterns, currently focused on service applications, but which could also be expanded to batch and test workloads in the future. While Docker itself works with individual containers, Kubernetes provides higher-level organizational constructs in support of common cluster-level usage patterns, currently focused on service applications, but which could also be expanded to batch and test workloads in the future.