Production-Grade Container Scheduling and Management
Go to file
Kubernetes Submit Queue 5dfea9e609 Merge pull request #51765 from mitake/etcd3-compaction
Automatic merge from submit-queue (batch tested with PRs 51765, 53053, 52771, 52860, 53284). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.

Add an option for turning on/off compaction from apiserver in etcd3 mode

…erver

**What this PR does / why we need it**:

This commit adds an option for controlling request of compaction to
etcd3 from apiserver. There is a situation that apiserver cannot fully
own its etcd cluster (e.g. sharing it with canal). In such a case,
apiserver should have limited access in terms of etcd's auth
functionality so it don't have a privilege to issue compaction
requests. It means that the compaction requests should be issued by
other component and apiserver's compaction requests are needless.

For such use cases, this commit adds a new flag
storagebackend.Config.DoCompaction. If the flag is true (default),
apiserver issues the compaction requests like current behaviour. If it
is false, apiserver doesn't issue the requests.

**Related issue (etcd)**
https://github.com/coreos/etcd/issues/8458
/cc @xiang90 @struz

**Release note:**
```release-note
Add --etcd-compaction-interval to apiserver for controlling request of compaction to etcd3 from apiserver.
```
2017-10-03 09:02:30 -07:00
.github Merge pull request #46714 from castrojo/new-issue-template 2017-06-22 16:43:47 -07:00
api Merge pull request #52950 from liggitt/persist-rbac-v1 2017-10-03 00:24:31 -07:00
build Merge pull request #49393 from hongchaodeng/etcd_update 2017-10-02 23:29:51 -07:00
cluster Merge pull request #52950 from liggitt/persist-rbac-v1 2017-10-03 00:24:31 -07:00
cmd Merge pull request #51765 from mitake/etcd3-compaction 2017-10-03 09:02:30 -07:00
docs Add 201/202 to the list of returned codes. 2017-09-28 12:25:39 -07:00
examples Merge pull request #52873 from ixdy/bazel-cleanup 2017-09-24 00:04:36 -07:00
federation Merge pull request #52950 from liggitt/persist-rbac-v1 2017-10-03 00:24:31 -07:00
Godeps Vendor godep v79 and use it 2017-09-29 15:16:09 -07:00
hack etcd: update version to 3.1.10 2017-10-02 12:27:46 -07:00
logo
pkg Merge pull request #52951 from kargakis/remove-dead-code 2017-10-03 08:11:04 -07:00
plugin Merge pull request #52723 from k82cn/k8s_42001_5 2017-10-03 05:15:20 -07:00
staging Merge pull request #51765 from mitake/etcd3-compaction 2017-10-03 09:02:30 -07:00
test Merge pull request #53271 from jennybuckley/patch-1 2017-10-03 05:15:23 -07:00
third_party Use buildozer to remove deprecated automanaged tags 2017-08-11 09:31:50 -07:00
translations Merge pull request #51463 from lucab85/i18n-Italian 2017-09-23 04:02:51 -07:00
vendor Vendor godep v79 and use it 2017-09-29 15:16:09 -07:00
.bazelrc move build related files out of the root directory 2017-05-15 15:53:54 -07:00
.generated_files
.gitattributes
.gitignore make clean will remove all gitignored files 2017-09-04 11:04:09 -07:00
.kazelcfg.json Switch from gazel to kazel, and move kazelcfg into build/root 2017-07-18 12:48:51 -07:00
BUILD.bazel move build related files out of the root directory 2017-05-15 15:53:54 -07:00
CHANGELOG-1.2.md Update TOC of CHANGELOG 2017-09-09 13:38:29 +08:00
CHANGELOG-1.3.md Move 1.3.* release notes out of CHANGELOG.md 2017-09-15 11:21:25 +08:00
CHANGELOG-1.4.md Move 1.4.* release notes out of CHANGELOG.md 2017-09-19 20:22:07 +08:00
CHANGELOG-1.5.md Move 1.5.* release notes out of CHANGELOG.md 2017-09-19 20:22:07 +08:00
CHANGELOG-1.6.md Move 1.6.11 changelog to CHANGELOG-1.6.md 2017-09-29 10:56:45 +08:00
CHANGELOG.md Update CHANGELOG.md for v1.5.8. 2017-09-30 22:16:44 -04:00
code-of-conduct.md
CONTRIBUTING.md
labels.yaml Merge pull request #51848 from xiangpengzhao/milestone-label 2017-09-05 15:46:19 -07:00
LICENSE
Makefile move build related files out of the root directory 2017-05-15 15:53:54 -07:00
Makefile.generated_files move build related files out of the root directory 2017-05-15 15:53:54 -07:00
OWNERS Fix my incorrect username in #46649 2017-08-10 11:59:54 -07:00
OWNERS_ALIASES Merge pull request #52108 from cmluciano/cml/addcmlucianomilestone 2017-09-23 07:14:00 -07:00
README.md Add CII Best Practices Badge 2017-08-22 10:56:16 -05:00
SUPPORT.md Add a SUPPORT.md file for github 2017-08-11 14:42:36 -04:00
Vagrantfile
WORKSPACE move build related files out of the root directory 2017-05-15 15:53:54 -07:00

Kubernetes

Submit Queue Widget GoDoc Widget CII Best Practices


Kubernetes is an open source system for managing containerized applications across multiple hosts, providing basic mechanisms for deployment, maintenance, and scaling of applications.

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.

Kubernetes is hosted by the Cloud Native Computing Foundation (CNCF). If you are a company that wants to help shape the evolution of technologies that are container-packaged, dynamically-scheduled and microservices-oriented, consider joining the CNCF. For details about who's involved and how Kubernetes plays a role, read the CNCF announcement.


To start using Kubernetes

See our documentation on kubernetes.io.

Try our interactive tutorial.

Take a free course on Scalable Microservices with Kubernetes.

To start developing Kubernetes

The community repository hosts all information about building Kubernetes from source, how to contribute code and documentation, who to contact about what, etc.

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

You have a working Go environment.
$ go get -d k8s.io/kubernetes
$ cd $GOPATH/src/k8s.io/kubernetes
$ make
You have a working Docker environment.
$ 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

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.

Analytics