Production-Grade Container Scheduling and Management
Go HTML Shell Python Protocol Buffer Makefile Other
Latest commit 9dd96e3 Jan 18, 2017 @k8s-merge-robot k8s-merge-robot committed on GitHub Merge pull request #39904 from jayunit100/scheduler_factory_iface_2
Automatic merge from submit-queue (batch tested with PRs 39898, 39904)

[scheduler] interface for config

**What this PR fixes**

This PR converts the Scheduler configuration factory into an interface, so that
- the scheduler_perf and scheduler integration tests dont rely on the struct for their implementation
- the exported functionality of the factory (i.e. what it needs to provide to create a scheduler configuration) is completely explicit, rather then completely coupled to a struct.
- makes some parts of the factory immutable, again to minimize possible coupling.  

This makes it easier to make a custom factory in instances where we might specifically want to import scheduler logic without actually reusing the entire scheduler codebase.
Permalink
Failed to load latest commit information.
.github Fix PR template Nov 11, 2016
Godeps bump(k8s.io/gengo):3c6a809462caf39389d70d9ea787ed24c5acffed Jan 16, 2017
api generated Jan 18, 2017
build Build release tarballs in bazel and add `make bazel-release` rule Jan 14, 2017
cluster Merge pull request #39898 from ixdy/bazel-release-tars Jan 18, 2017
cmd Merge pull request #39625 from deads2k/rbac-36-beta Jan 18, 2017
docs generated Jan 18, 2017
examples Merge pull request #39709 from smarterclayton/object_meta Jan 17, 2017
federation Merge pull request #39898 from ixdy/bazel-release-tars Jan 18, 2017
hack Merge pull request #39898 from ixdy/bazel-release-tars Jan 18, 2017
hooks Fix spelling in package naming linter error message Dec 20, 2016
logo Update usage guidelines to reflect the donation to CNCF Oct 12, 2016
pkg Merge pull request #39042 from juanvallejo/jvallejo/dont-filter-pods-… Jan 18, 2017
plugin Merge pull request #39904 from jayunit100/scheduler_factory_iface_2 Jan 18, 2017
staging Merge pull request #40041 from deads2k/generic-25-undo-admission Jan 18, 2017
test Merge pull request #39904 from jayunit100/scheduler_factory_iface_2 Jan 18, 2017
third_party Build release tarballs in bazel and add `make bazel-release` rule Jan 14, 2017
translations Add initial translation support. Dec 24, 2016
vendor Merge pull request #40041 from deads2k/generic-25-undo-admission Jan 18, 2017
.gazelcfg.json Generate a dummy BUILD file in _output/local/go to keep Bazel out of … Jan 6, 2017
.generated_docs add create rolebinding Dec 21, 2016
.generated_files List generated files for the github size munger Nov 15, 2016
.gitattributes Add -diff attributes for generated files Dec 9, 2016
.gitignore Add verbose mode to boilerplate Oct 23, 2016
BUILD.bazel Add release-tars to ci-artifacts Jan 14, 2017
CHANGELOG.md Update CHANGELOG.md for v1.5.2. Jan 12, 2017
CONTRIBUTING.md updated munge-docs Nov 29, 2016
LICENSE LICENSE: revert modifications to Apache license Nov 22, 2016
Makefile Build release tarballs in bazel and add `make bazel-release` rule Jan 14, 2017
Makefile.generated_files Remove a from each codegen path Dec 31, 2016
OWNERS Add jbeda to top level OWNERS Oct 25, 2016
OWNERS_ALIASES OWNERS: Create sig-node alias Jan 18, 2017
README.md Update README.md Dec 20, 2016
Vagrantfile Customizable vagrant rsync args and excludes Nov 14, 2016
WORKSPACE Merge pull request #39898 from ixdy/bazel-release-tars Jan 18, 2017
code-of-conduct.md Change code of conduct to call CNCF CoC by reference Oct 19, 2016
labels.yaml Updating labels.yaml to add labels: cncf-cla:yes and cncf-cla:no Oct 3, 2016

README.md

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