github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #53 from asm89/patch-1 

Update DESIGN.md
pull/6/head
Daniel Smith 2014-06-10 20:09:24 -07:00
parent 8b9e504574 5b6879a932
commit e4b24bd0a7
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
DESIGN.md
View File

@ -67,7 +67,7 @@ It validates and configures data for 3 types of objects:
* `pod`: Each `pod` has a representation at the Kubernetes API level.
* `service`: A service is a configuration unit for the proxies that run on every worker node. It is named and points to one or more Pods.
* `replicationController`: A replication controller takes a template and ensures that there is a specified number of "replicas" of that template running at any one time. If there are too many, it'll start more. If there are too few, it'll kill some.
* `replicationController`: A replication controller takes a template and ensures that there is a specified number of "replicas" of that template running at any one time. If there are too many, it'll kill some. If there are too few, it'll start more.
Beyond just servicing REST operations, validating them and storing them in `etcd`, the API Server does two other things: