Repository files navigation

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

Kubernetes is an open source system for managingcontainerized 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 adecade and a half of experience at Google running production workloads at scale, combined with best-of-breed ideas and practices from the community.

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.

With the1.0.1 release Kubernetes is ready to serve your production workloads.

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 theGetting 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 runningat 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.

Kubernetes documentation is organized into several categories.

• Getting started guides
  • for people who want to create a Kubernetes cluster
    • inCreating a Kubernetes Cluster
  • for people who want to port Kubernetes to a new environment
    • inGetting Started from Scratch
• User documentation
  • for people who want to run programs on an existing Kubernetes cluster
  • in theKubernetes User Guide: Managing Applications
  • theKubectl Command Line Interface is a detailed reference onthekubectl CLI
  • User FAQ
• Cluster administrator documentation
  • for people who want to create a Kubernetes cluster and administer it
  • in theKubernetes Cluster Admin Guide
• Developer and API documentation
  • for people who want to write programs that access the Kubernetes API, write pluginsor extensions, or modify the core Kubernetes code
  • in theKubernetes Developer Guide
  • see alsonotes on the API
  • see also theAPI object documentation, adetailed description of all fields found in the core API objects
• Walkthroughs and examples
  • hands-on introduction and example config files
  • in theuser guide
  • in thedocs/examples directory
• Contributions from the Kubernetes community
  • in thedocs/contrib directory
• Design documentation and design proposals
  • for people who want to understand the design of Kubernetes, and feature proposals
  • design docs in theKubernetes Design Overview and thedocs/design directory
  • proposals in thedocs/proposals directory
• Wiki/FAQ
  • in thewiki
  • troubleshooting information in thetroubleshooting guide

If you have questions or want to start contributing please reach out. We don't bite!

Please see thetroubleshooting guide, or how toget more help.

If you are a company and are looking for a more formal engagement with Google around Kubernetes and containers at Google as a whole, please fill outthis form and we'll be in touch.