Lightweight Kubernetes
 
 
 
 
Go to file
k8s-merge-robot 34094635ba Merge pull request #22880 from spxtr/aws-job
Auto commit by PR queue bot
2016-03-14 20:41:42 -07:00
Godeps Merge pull request #22892 from ixdy/verify-all 2016-03-12 04:33:17 -08:00
api/swagger-spec add FullyLabeledReplicas in Replicaset Status and ReplicationController Status 2016-03-11 23:55:04 -08:00
build add proxy settings for vagrant 2016-03-07 09:57:26 +08:00
cluster Heapster sizing adjustments 2016-03-14 20:00:17 +01:00
cmd Tolerate multiple registered versions in a single group 2016-03-12 12:49:41 -05:00
contrib added proxy-kubeconfig flag 2016-03-10 20:35:49 -05:00
docs generating 2016-03-14 14:59:39 -07:00
examples Merge pull request #21899 from zmerlynn/update-spark 2016-03-12 07:25:17 -08:00
hack Merge pull request #22880 from spxtr/aws-job 2016-03-14 20:41:42 -07:00
hooks Spelling fixes inspired by github.com/client9/misspell 2016-02-18 06:58:05 +07:00
pkg Merge pull request #22899 from justinsb/aws_fix_e2e 2016-03-14 17:37:13 -07:00
plugin Reduce namespace deletion test flakes by forcing a cache refresh when a namespace is initially deleted 2016-03-14 16:08:01 -04:00
release Merge pull request #22329 from david-mcmahon/push-official 2016-03-03 08:52:35 -08:00
test Merge pull request #22955 from lavalamp/fix-22238 2016-03-14 19:26:26 -07:00
third_party Fix a couple typos 2016-02-02 15:39:33 -05:00
www add back missing analytics link 2015-08-13 10:03:07 -07:00
.generated_docs added 'kubectl create sa' to create serviceaccounts 2016-02-26 10:27:37 -05:00
.gitignore Add direnv .envrc files to gitignore 2016-02-13 01:20:17 -05:00
.travis.yml Update tests from Go 1.5.2 to Go 1.5.3 2016-01-21 09:43:52 -08:00
CHANGELOG.md s|github.com/GoogleCloudPlatform/kubernetes|github.com/kubernetes/kubernetes| 2015-09-03 10:10:11 -04:00
CONTRIB.md Add ga-beacon analytics to gendocs scripts 2015-05-15 18:56:38 -07:00
CONTRIBUTING.md Update advice for getting support and filing issues. 2015-08-19 03:18:06 +00:00
DESIGN.md Fix links in DESIGN.md 2015-07-20 14:35:52 -07:00
LICENSE Fix LICENSE file. 2016-02-24 16:41:19 -08:00
Makefile Revert "Disable verify-godep-licenses.sh in hack/verify-all.sh" 2016-03-11 17:31:56 -08:00
README.md Add GoReportCard to main README 2016-03-03 13:57:29 -08:00
Vagrantfile add proxy settings for vagrant 2016-03-07 09:57:26 +08:00
code-of-conduct.md Add a code of conduct. 2015-09-10 11:53:27 -07:00
logo.pdf Simplify the SVG for the logo 2015-02-20 21:15:31 -08:00
logo.png change logo blue slightly 2014-08-15 09:54:00 -07:00
logo.svg Simplify the SVG for the logo 2015-02-20 21:15:31 -08:00
logo_usage_guidelines.md s|github.com/GoogleCloudPlatform/kubernetes|github.com/kubernetes/kubernetes| 2015-09-03 10:10:11 -04:00
shippable.yml Refactor hack/verify-all.sh and run almost all checks. 2016-03-09 15:20:36 -08:00

README.md

Kubernetes

GoReportCard Widget GoDoc Widget Travis Widget Coverage Status Widget

Are you ...

  • Interested in learning more about using Kubernetes? Please see our user-facing documentation on kubernetes.io
  • Interested in hacking on the core Kubernetes code base? Keep reading!

Kubernetes is an open source system for managing containerized applications across multiple hosts, providing basic mechanisms for deployment, maintenance, and scaling of applications.

Kubernetes is:

  • lean: lightweight, simple, accessible
  • portable: public, private, hybrid, multi cloud
  • extensible: modular, pluggable, hookable, composable
  • self-healing: auto-placement, auto-restart, auto-replication

Kubernetes builds upon a decade and a half of experience at Google running production workloads at scale, combined with best-of-breed ideas and practices from the community.


Kubernetes can run anywhere!

However, initial development was done on GCE and so our instructions and scripts are built around that. If you make it work on other infrastructure please let us know and contribute instructions/code.

Kubernetes is ready for Production!

With the 1.0.1 release Kubernetes is ready to serve your production workloads.

Concepts

Kubernetes works with the following concepts:

Cluster
A cluster is a set of physical or virtual machines and other infrastructure resources used by Kubernetes to run your applications. Kubernetes can run anywhere! See the Getting Started Guides for instructions for a variety of services.
Node
A node is a physical or virtual machine running Kubernetes, onto which pods can be scheduled.
Pod
Pods are a colocated group of application containers with shared volumes. They're the smallest deployable units that can be created, scheduled, and managed with Kubernetes. Pods can be created individually, but it's recommended that you use a replication controller even if creating a single pod.
Replication controller
Replication controllers manage the lifecycle of pods. They ensure that a specified number of pods are running at any given time, by creating or killing pods as required.
Service
Services provide a single, stable name and address for a set of pods. They act as basic load balancers.
Label
Labels are used to organize and select groups of objects based on key:value pairs.

Documentation

Kubernetes documentation is organized into several categories.

Community, discussion, contribution, and support

See which companies are committed to driving quality in Kubernetes on our community page.

Do you want to help "shape the evolution of technologies that are container packaged, dynamically scheduled and microservices oriented?"

You should consider joining the Cloud Native Computing Foundation. For details about who's involved and how Kubernetes plays a role, read their announcement.

Code of conduct

Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.

Are you ready to add to the discussion?

We have presence on:

You can also view recordings of past events and presentations on our Media page.

For Q&A, our threads are at:

Want to do more than just 'discuss' Kubernetes?

If you're interested in being a contributor and want to get involved in developing Kubernetes, start in the Kubernetes Developer Guide and also review the contributor guidelines.

Support

While there are many different channels that you can use to get ahold of us, you can help make sure that we are efficient in getting you the help that you need.

If you need support, start with the troubleshooting guide and work your way through the process that we've outlined.

That said, if you have questions, reach out to us one way or another. We don't bite!

Analytics