Go to file
Isaac Hollander McCreery 83bfe2cfda Refactor e2e.sh in preparation for YAML-ifying configs
Remove E2E_CLUSTER_NAME, E2E_NETWORK, and KUBE_GCE_INSTANCE_PREFIX from jobs that don't need them, because they are in their own project, and add defaults

Fail on leaked resources by default

Kill E2E_SET_CLUSTER_API_VERSION

Rely on defaults for E2E_UP, E2E_TEST, E2E_DOWN

Only PUBLISH_GREEN_VERSION for kubernetes-e2e-gce

Directly export ZONE vars rather than chaining and setting locals

Collapse E2E_CLUSTER_NAME, E2E_NETWORK, and KUBE_GCE_INSTANCE_PREFIX into E2E_NAME (always take the shortest of the three, to avoid name length problems

Factor out soak vars

Remove incorrect feature enablement ENV vars

export GINKGO_TEST_ARGS directly, rather than looping through export at the bottom

Directly export E2E Control Variables

Export KUBEMARK ENV vars directly

export KUBERNETES_PROVIDER directly

Export JENKINS_PUBLISHED_VERSION directly, and don't use it where unnecessary; remove old CURRENT_RELEASE_PUBLISHED_VERSION

export PROJECT and NETWORK_PROVIDER directly

export node ENV vars directly

export other shared cluster ENV vars directly

Directly export CLOUDSDK ENV vars

export GCE and AWS ENVs directly

Various cleanup, including refactoring upgrades

Fixup: no PERFORMANCE env for AWS

Address comment

Fixes for comments up to cebf501

Address comments through 81f39b8

Fix: default E2E_UP, E2E_TEST, E2E_DOWN

Use JENKINS_FORCE_GET_TARS for upgrade jobs; fixes through 140ea2b

Fix ubernetes-lite config

Address rebased 2 comments

Remove tab
2016-02-17 11:28:18 -08:00
api/swagger-spec Support the subresource of node proxy 2016-02-16 17:02:45 +08:00
build Merge pull request #21031 from zmerlynn/distribute-source 2016-02-14 11:12:18 -08:00
cluster Merge pull request #21161 from justinsb/aws_bootstrap_on_every_boot 2016-02-17 06:45:24 -08:00
cmd Merge pull request #20063 from mqliang/imageGC-config 2016-02-17 06:16:45 -08:00
contrib Merge pull request #21325 from caesarxuchao/coding-conventions 2016-02-16 13:00:13 -08:00
docs Merge pull request #18010 from feihujiang/supportSubresourceOfNodeProxy 2016-02-17 08:15:50 -08:00
examples Merge pull request #21345 from CenturyLinkCloud/master 2016-02-17 02:26:51 -08:00
Godeps Merge pull request #21198 from mesosphere/jdef_update_mgo_latest 2016-02-16 06:37:42 -08:00
hack Refactor e2e.sh in preparation for YAML-ifying configs 2016-02-17 11:28:18 -08:00
hooks linkchecker tool now visits the URL to determine if it's valid 2016-01-26 17:01:37 -08:00
pkg Merge pull request #19771 from derekwaynecarr/field_selector 2016-02-17 09:20:40 -08:00
plugin Merge pull request #21074 from mqliang/scheduler-ReplicaSet 2016-02-16 01:48:33 -08:00
release Push docker images for cluster components during release. 2016-01-05 12:36:10 +01:00
test Merge pull request #18010 from feihujiang/supportSubresourceOfNodeProxy 2016-02-17 08:15:50 -08: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 Add kubectl rollout undo 2016-02-02 14:20:01 -08: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
code-of-conduct.md Add a code of conduct. 2015-09-10 11:53:27 -07: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 First commit 2014-06-06 16:40:48 -07:00
logo_usage_guidelines.md s|github.com/GoogleCloudPlatform/kubernetes|github.com/kubernetes/kubernetes| 2015-09-03 10:10:11 -04: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
Makefile Add boilerplate checks for Makefiles 2016-02-03 18:35:26 -05:00
README.md Add aliases for links and link widgets 2015-09-15 14:39:05 +03:00
shippable.yml linkchecker tool now visits the URL to determine if it's valid 2016-01-26 17:01:37 -08:00
Vagrantfile Updated Vagrant VMs to Fedora 23 2016-01-19 16:52:54 +00:00

Kubernetes

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