Production-Grade Container Scheduling and Management
Go to file
Phillip Wittrock 3de94cd23c Supply volume fs metrics to server/stats/handler.go
* Metrics will not be expose until they are hooked up to a handler
* Metrics are not cached and expose a dos vector, this must be fixed before release or the stats should not be exposed through an api endpoint
2016-02-05 16:00:24 -08:00
api/swagger-spec Merge pull request #20142 from bprashanth/ing_tls 2016-02-05 15:07:09 -08:00
build Merge pull request #20545 from pmorie/boilerplate 2016-02-03 19:46:26 -08:00
cluster Merge pull request #20650 from mwielgus/heapster-alpha4 2016-02-05 16:04:41 +01:00
cmd Supply volume fs metrics to server/stats/handler.go 2016-02-05 16:00:24 -08:00
contrib Merge pull request #19689 from AdoHe/kubectl_label_display 2016-02-05 14:08:37 -08:00
docs Supply volume fs metrics to server/stats/handler.go 2016-02-05 16:00:24 -08:00
examples Merge pull request #20513 from nikhiljindal/apiserverExampleTest 2016-02-04 11:28:58 -08:00
Godeps Merge pull request #20094 from mesosphere/jdef_mesos_026_godeps 2016-02-02 03:19:25 -08:00
hack Supply volume fs metrics to server/stats/handler.go 2016-02-05 16:00:24 -08:00
hooks linkchecker tool now visits the URL to determine if it's valid 2016-01-26 17:01:37 -08:00
pkg Supply volume fs metrics to server/stats/handler.go 2016-02-05 16:00:24 -08:00
plugin Merge pull request #19880 from DirectXMan12/feature/limit-ebs-scheduler-predicate 2016-02-05 09:26:42 -08:00
release Push docker images for cluster components during release. 2016-01-05 12:36:10 +01:00
test Supply volume fs metrics to server/stats/handler.go 2016-02-05 16:00:24 -08:00
third_party Fix a couple typos 2016-02-02 15:39:33 -05:00
www
.generated_docs Add kubectl rollout undo 2016-02-02 14:20:01 -08:00
.gitignore Add ./kubernetes to .gitignore 2016-01-13 12:36:20 +05:30
.travis.yml Update tests from Go 1.5.2 to Go 1.5.3 2016-01-21 09:43:52 -08:00
CHANGELOG.md
code-of-conduct.md
CONTRIB.md
CONTRIBUTING.md
DESIGN.md
LICENSE
logo_usage_guidelines.md
logo.pdf
logo.png
logo.svg
Makefile Add boilerplate checks for Makefiles 2016-02-03 18:35:26 -05:00
README.md
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