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

Documentation additions and refactoring. #481

Merged
merged 1 commit into from
Jul 16, 2014
Merged

Documentation additions and refactoring. #481

merged 1 commit into from
Jul 16, 2014

Conversation

bgrant0607
Copy link
Member

Added networking documentation from #188 and #15. Moved most pod, label, and network documentation to separate docs. Added minimal service documentation (more to do there).


### Pods

A `pod` (as in a pod of whales or pea pod) is a relatively tightly coupled group of containers that are scheduled onto the same physical node. In addition to defining the containers that run in the pod, the containers in the pod all use the same network namespace/IP (and port space), and define a set of shared storage volumes. Pods facilitate data sharing and IPC among their constituents, serve as units of scheduling, deployment, and horizontal scaling/replication, and share fate. In the future, they may share resources ([LPC2013](http://www.linuxplumbersconf.org/2013/ocw//system/presentations/1239/original/lmctfy%20(1).pdf)).
A _pod_ (as in a pod of whales or pea pod) is a relatively tightly coupled group of containers that are scheduled onto the same host. It models an application-specific "virtual host" in a containerized environment. Pods serve as units of scheduling, deployment, and horizontal scaling/replication, share fate, and share some resources, such as storage volumes.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"... share some resources, such as storage volumes and IP addresses."

@brendandburns
Copy link
Contributor

Couple of small comments but basically LGTM.

@bgrant0607
Copy link
Member Author

Addressed comments. PTAL.

@lavalamp
Copy link
Member

LGTM. Can you squash the commits?

@brendandburns
Copy link
Contributor

git rebase -i HEAD~4 (in case you hadn't squashed commits before)

…d networking documentation to push details into separate documents. Add some documentation of how to connect to services.
@lavalamp
Copy link
Member

Thanks!

lavalamp added a commit that referenced this pull request Jul 16, 2014
Documentation additions and refactoring.
@lavalamp lavalamp merged commit 0e1636e into kubernetes:master Jul 16, 2014
vishh added a commit to vishh/kubernetes that referenced this pull request Apr 6, 2016
Initial types for stats summary.
seans3 pushed a commit to seans3/kubernetes that referenced this pull request Apr 10, 2019
Add deprecation notice for `openstack-heat`
jsafrane pushed a commit to jsafrane/kubernetes that referenced this pull request Dec 15, 2020
…aster

Bug 1770017: kubelet: do not rerun init containers if any main containers have status
linxiulei pushed a commit to linxiulei/kubernetes that referenced this pull request Jan 18, 2024
Adapt OOMKilling pattern to old and new Linux kernels
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants