Production-Grade Container Scheduling and Management
Go to file
Solly Ross d6fe1e8764 HPA Controller: Use Custom Metrics API
This commit switches over the HPA controller to use the custom metrics
API.  It also converts the HPA controller to use the generated client
in k8s.io/metrics for the resource metrics API.

In order to enable support, you must enable
`--horizontal-pod-autoscaler-use-rest-clients` on the
controller-manager, which will switch the HPA controller's MetricsClient
implementation over to use the standard rest clients for both custom
metrics and resource metrics.  This requires that at the least resource
metrics API is registered with kube-aggregator, and that the controller
manager is pointed at kube-aggregator.  For this to work, Heapster
must be serving the new-style API server (`--api-server=true`).
2017-03-01 10:21:50 -05:00
.github Fix issue template to read more clearly 2017-01-27 10:15:06 -07:00
api generated 2017-02-28 23:05:40 -08:00
build Merge pull request #42090 from timstclair/kube-proxy 2017-03-01 04:10:06 -08:00
cluster Merge pull request #41949 from Random-Liu/collect-npd-log 2017-03-01 04:10:08 -08:00
cmd HPA Controller: Use Custom Metrics API 2017-03-01 10:21:50 -05:00
docs generated 2017-02-28 23:05:40 -08:00
examples Portworx Volume Driver in Kubernetes 2017-02-28 23:24:56 +00:00
federation API 2017-02-28 23:05:40 -08:00
Godeps Portworx Volume Driver in Kubernetes 2017-02-28 23:24:56 +00:00
hack HPA Controller: Use Custom Metrics API 2017-03-01 10:21:50 -05:00
hooks Fix spelling in package naming linter error message 2016-12-20 15:48:14 -05:00
logo Updated top level owners file to match new format 2017-01-19 11:29:16 -08:00
pkg HPA Controller: Use Custom Metrics API 2017-03-01 10:21:50 -05:00
plugin Merge pull request #41708 from bsalamat/statefulset_spreading2 2017-02-28 20:16:08 -08:00
staging Remove comment from all staging Godeps.json 2017-03-01 12:56:39 +01:00
test Merge pull request #42116 from vishh/gpu-experimental-support 2017-03-01 04:52:50 -08:00
third_party Add forked etcd 2.2.1 code to allow rollback to 2.2.1 version 2017-02-10 13:56:01 +01:00
translations Update extraction script, sort messages, add .pot file. 2017-02-23 18:53:00 +00:00
vendor Merge pull request #38676 from caesarxuchao/sync-gc 2017-03-01 01:44:02 -08:00
.bazelrc Add verify-gofmt as a Bazel test. 2017-02-10 17:00:28 -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_files Move .generated_docs to docs/ so docs OWNERS can review / approve 2017-02-16 10:11:57 -08:00
.gitattributes Add -diff attributes for generated files 2016-12-08 17:12:07 -08:00
.gitignore Add cscope related files into .gitignore. 2016-12-21 10:35:14 +08:00
BUILD.bazel bazel: save git version in kubernetes.tar.gz 2017-01-23 17:28:08 -08:00
CHANGELOG.md Update CHANGELOG.md for v1.6.0-alpha.3. 2017-02-16 12:13:13 -08:00
code-of-conduct.md Change code of conduct to call CNCF CoC by reference 2016-10-19 13:22:35 -04:00
CONTRIBUTING.md updated munge-docs 2016-11-29 01:35:11 -08:00
labels.yaml Updating labels.yaml to add labels: cncf-cla:yes and cncf-cla:no 2016-10-03 09:54:42 -07:00
LICENSE LICENSE: revert modifications to Apache license 2016-11-22 11:44:46 -08:00
Makefile Make make quick-release quick again 2017-02-21 14:35:55 -08:00
Makefile.generated_files Remove a from each codegen path 2016-12-30 18:44:32 -08:00
OWNERS Add wojtec to global approvers 2017-01-25 11:57:00 -06:00
OWNERS_ALIASES add OWNER file to kubelet/network 2017-02-24 11:41:13 -08:00
README.md Tidy up the main README. 2017-02-01 20:13:09 -08:00
Vagrantfile Customizable vagrant rsync args and excludes 2016-11-14 11:18:44 +01:00
WORKSPACE upgrade to latest build rules 2017-02-01 15:16:43 -08:00

Kubernetes

Submit Queue Widget GoDoc 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.

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