Production-Grade Container Scheduling and Management
Go to file
Kubernetes Submit Queue d28fccfabe
Merge pull request #55261 from ncdc/kube-proxy-config-fix-conntrack-zero-values
Automatic merge from submit-queue (batch tested with PRs 55247, 55324, 55261, 55147, 54052). 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>.

Restore kube-proxy's support for 0 values for conntrack settings

**What this PR does / why we need it**: re-allow 0 values for kube-proxy conntrack min, max, max per core, tcp close wait timeout, tcp established timeout.

**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
Fixes #50787

**Special notes for your reviewer**:
- I adjusted validation to allow for 0 values for some of the conntrack settings, as otherwise the "leave the limit as-is" logic wouldn't be allowed.
- I moved the loading of the config file from the cobra command's Validate method to Complete. This way, the config is fully resolved before validation happens. Otherwise, it just validates the default config values first, and _then_ the config is loaded.
- I think I got all the default values & nil checking correct, but please review carefully!

**Release note**:

```release-note
Restored kube-proxy's support for 0 values for conntrack min, max, max per core, tcp close wait timeout, and tcp established timeout.
```
2017-11-09 00:59:23 -08:00
.github Merge pull request #54114 from xiangpengzhao/fix-pr-template 2017-10-30 18:37:06 -07:00
api Merge pull request #55272 from janetkuo/ds-conditions 2017-11-08 17:13:19 -08:00
build Merge pull request #47497 from mikedanese/binary 2017-11-08 22:11:53 -08:00
cluster Merge pull request #55324 from xiangpengzhao/gce-update 2017-11-09 00:59:20 -08:00
cmd Merge pull request #55261 from ncdc/kube-proxy-config-fix-conntrack-zero-values 2017-11-09 00:59:23 -08:00
docs Merge pull request #55272 from janetkuo/ds-conditions 2017-11-08 17:13:19 -08:00
examples Update storageclass version to v1 in examples 2017-11-01 13:05:29 +08:00
Godeps Merge pull request #54786 from shiywang/bump-protobuf 2017-11-06 20:39:05 -08:00
hack Merge pull request #47497 from mikedanese/binary 2017-11-08 22:11:53 -08:00
logo Don't use strokes in the logo SVG 2017-10-12 09:38:56 -07:00
pkg Merge pull request #55261 from ncdc/kube-proxy-config-fix-conntrack-zero-values 2017-11-09 00:59:23 -08:00
plugin Merge pull request #55311 from CaoShuFeng/scheduler-trivial 2017-11-08 19:31:15 -08:00
staging Merge pull request #54267 from ericchiang/audit-policy-file-without-kind-or-version 2017-11-08 22:56:34 -08:00
test Merge pull request #49429 from enisoc/dedup-rc-rs 2017-11-08 22:12:03 -08:00
third_party Merge pull request #47699 from supereagle/fix-typos 2017-10-17 02:35:52 -07:00
translations Merge pull request #51463 from lucab85/i18n-Italian 2017-09-23 04:02:51 -07:00
vendor Merge pull request #54786 from shiywang/bump-protobuf 2017-11-06 20:39:05 -08:00
.bazelrc
.generated_files
.gitattributes Hide openapi-spec in diffs 2017-11-04 23:16:04 -07:00
.gitignore make clean will remove all gitignored files 2017-09-04 11:04:09 -07:00
.kazelcfg.json
BUILD.bazel
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 Update invalid TOC anchor of 1.4 CHANGELOG 2017-10-26 17:25:23 +08:00
CHANGELOG-1.5.md Regenerate CHANGELOG TOCs 2017-10-11 17:04:47 -04:00
CHANGELOG-1.6.md Update invalid TOC anchor of 1.6 CHANGELOG 2017-10-26 17:25:34 +08:00
CHANGELOG-1.7.md Update CHANGELOG-1.7.md for v1.7.10. 2017-11-03 16:39:03 -04:00
CHANGELOG-1.8.md Merge pull request #54267 from ericchiang/audit-policy-file-without-kind-or-version 2017-11-08 22:56:34 -08:00
CHANGELOG-1.9.md Update CHANGELOG-1.9.md for v1.9.0-alpha.2. 2017-11-01 15:32:46 -07:00
CHANGELOG.md Move 1.8.x release notes 2017-10-11 22:41:36 -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
Makefile.generated_files
OWNERS
OWNERS_ALIASES Add bsalamat to milestone maintainers 2017-10-26 10:25:42 -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

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