Production-Grade Container Scheduling and Management
Go to file
Matt Bruzek 3fcf279cfb Splitting master/node services into separate charm layers
This branch includes a rollup series of commits from a fork of the
kubernetes repository pre 1.5 release because we didn't make the code freeze.
This additional effort has been fully tested and has results submit into
the gubernator to enhance confidence in this code quality vs. the single
layer, posing as both master/node.

To reference the gubernator results, please see:
https://k8s-gubernator.appspot.com/builds/canonical-kubernetes-tests/logs/kubernetes-gce-e2e-node/

Apologies in advance for the large commit, however we did not want to
submit without having successful upstream automated testing results.

This commit includes:

 - Support for CNI networking plugins
 - Support for durable storage provided by ceph
 - Building from upstream templates (read: kubedns - no more template
 drift!)
 - An e2e charm-layer to make running validation tests much simpler/repeatable
 - Changes to support the 1.5.x series of kubernetes

Additional note: We will be targeting -all- future work against upstream
so large pull requests of this magnitude will not occur again.
2017-01-24 09:42:25 -06:00
.github
api generated: api 2017-01-23 12:26:35 -05:00
build Merge pull request #40120 from ixdy/bazel-release-tars 2017-01-20 16:19:09 -08:00
cluster Splitting master/node services into separate charm layers 2017-01-24 09:42:25 -06:00
cmd Merge pull request #40309 from apelisse/complete-owners 2017-01-23 11:24:51 -08:00
docs generated: api 2017-01-23 12:26:35 -05:00
examples Merge pull request #39199 from deimosfr/cassandra_exemple_fix_shutdown 2017-01-23 00:30:11 -08:00
federation Merge pull request #40205 from madhusudancs/fed-remove-federated-image-tag-dep 2017-01-23 13:12:52 -08:00
Godeps bump:(github.com/armon/circbuf):bbbad097214e2918d8543d5201d12bfd7bca254d 2017-01-23 12:25:56 -05:00
hack Splitting master/node services into separate charm layers 2017-01-24 09:42:25 -06:00
hooks
logo Updated top level owners file to match new format 2017-01-19 11:29:16 -08:00
pkg Merge pull request #40208 from wojtek-t/smart_volume_manager 2017-01-23 13:40:03 -08:00
plugin OWNERS: Update latest OWNERS files 2017-01-23 10:05:48 -08:00
staging OWNERS: Update latest OWNERS files 2017-01-23 10:05:48 -08:00
test Add conformance tests for terminationMessage(Path|Policy) 2017-01-23 12:26:37 -05:00
third_party Build release tarballs in bazel and add make bazel-release rule 2017-01-13 16:17:44 -08:00
translations
vendor generated: api 2017-01-23 12:26:35 -05:00
.bazelrc Add .bazelrc with flaky_test_attempts. 2017-01-20 11:41:33 -08:00
.gazelcfg.json Generate a dummy BUILD file in _output/local/go to keep Bazel out of trouble 2017-01-05 22:05:17 -08:00
.generated_docs Add the ability to edit fields within a config map. 2017-01-14 21:12:27 -08:00
.generated_files
.gitattributes
.gitignore
BUILD.bazel Add release-tars to ci-artifacts 2017-01-13 16:34:06 -08:00
CHANGELOG.md Update CHANGELOG.md for v1.5.2. 2017-01-11 23:06:30 -08:00
code-of-conduct.md
CONTRIBUTING.md
labels.yaml
LICENSE
Makefile Add .bazelrc with flaky_test_attempts. 2017-01-20 11:41:33 -08:00
Makefile.generated_files
OWNERS Updated top level owners file to match new format 2017-01-19 11:29:16 -08:00
OWNERS_ALIASES OWNERS: Create sig-node alias 2017-01-17 16:25:40 -08:00
README.md
Vagrantfile
WORKSPACE Merge pull request #39898 from ixdy/bazel-release-tars 2017-01-18 14:24:48 -08:00

Kubernetes

Submit Queue Widget GoDoc Widget Coverage Status Widget

Introduction

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 hosted by the Cloud Native Computing Foundation (CNCF)

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


Are you ...

Code of Conduct

The Kubernetes community abides by the CNCF code of conduct. Here is an excerpt:

As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.

Community

Do you want to help "shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented? ". If you are a company, you should consider joining the CNCF. For details about who's involved in CNCF and how Kubernetes plays a role, read the announcement. For general information about our community see the website community page.

Join us on social media (Twitter, Google+) and read our blog

Ask questions and help answer them on Slack or Stack Overflow

Attend our key events (kubecon, cloudnativecon, weekly community meeting)

Join a Special Interest Group (SIG)

Contribute

If you're interested in being a contributor and want to get involved in developing Kubernetes, get started with this reading:

You will then most certainly gain a lot from joining a SIG, attending the regular hangouts as well as the community meeting.

If you have an idea for a new feature, see the Kubernetes Features repository for a list of features that are coming in new releases as well as details on how to propose one.

Building Kubernetes for the impatient

If you want to build Kubernetes right away there are two options:

$ go get -d k8s.io/kubernetes
$ cd $GOPATH/src/k8s.io/kubernetes
$ make
$ git clone https://github.com/kubernetes/kubernetes
$ cd kubernetes
$ make quick-release

If you are less impatient, head over to the developer's documentation.

Support

While there are many different channels that you can use to get hold of us (Slack, Stack Overflow, Issues, Forums/Mailing lists), 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