This repository has been archived by the owner on Apr 3, 2023. It is now read-only.
Code changes from upstream 1.11.10 #18
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…xInt32. 1. MaxInt32 has the same meaning as unset, for compatibility 2. Deployment controller treats MaxInt32 the same as unset (nil)
Fixes kubernetes#70033 Signed-off-by: Harsh Desai <harsh@portworx.com>
- reused client whenever possible - refactor get client function into explicit cluster-wide and local functions Signed-off-by: Harsh Desai <harsh@portworx.com>
Add test for verifying volume detach
A volume can show up as in-use even before it gets attached to the node.
… setupCluster to make resync period of scheduler configurable. - Add test case for static provisioning and delay binding storage class. Move pods into active queue on PV add/update events. - Add a stress test with scheduler resync to detect possible race conditions.
UnmountDevice must not clear devicepath, because such devicePath may come from node.status (e.g. on AWS) and subsequent MountDevice operation (that may be already enqueued) needs it.
Bump golang to 1.10.7 (CVE-2018-16875)
fix gofmt issue
…k-of-#71834-upstream-release-1.11 Automated cherry pick of kubernetes#71834 / kubernetes#71114 upstream release 1.11
The pull-kubernetes-verify presubmit is failing on verify-cloudprovider-gce.sh because it is a new year and thus current test generated code doesn't match the prior committed generated code in the copyright header. The verifier is removed in master now, so for simplicity and rather than fixing the verifier to ignore the header differences for prior supported branched, this commit is the result of rerunning hack/update-cloudprovider-gce.sh. Signed-off-by: Tim Pepper <tpepper@vmware.com>
…headerfixup update cloud provider boilerplate
…ck-of-#70392-upstream-release-1.11 Automated cherry pick of kubernetes#70392: Lookup PX api port from k8s service
…-of-#65616-upstream-release-1.11 Automated cherry pick of kubernetes#65616: Retry scheduling on various events.
…k-of-#72361-upstream-release-1.11 Automated cherry pick of kubernetes#72361 upstream release 1.11
Azure VM and vmssVM support multiple backend pools for the same SLB, but not for different LBs.
…-pick-of-#76211-upstream-release-1.11 Automated cherry pick of kubernetes#76211 to release-1.11: Use Node-Problem-Detector v0.6.3 on GCI
…ck-of-#72621-upstream-release-1.11 Automated cherry pick of kubernetes#72621: Increase default maximumLoadBalancerRuleCount to 250
…ck-of-#76691-upstream-release-1.11 Automated cherry pick of kubernetes#76691: Fix Azure SLB support for multiple backend pools
Bump debian-iptables to v11.0.2
…-of-#75746-upstream-release-1.11 Automated cherry pick of kubernetes#75746: Updated regional PD minimum size; changed regional PD
…-of-#75362-upstream-release-1.11 Automated cherry pick of kubernetes#75362: Update gcp images with security patches
…k-of-#75411-upstream-release-1.11 Automated cherry pick of kubernetes#75411: disable HTTP2 ingress test
This is equivalent to the "internal" firewall rule that is created for the regular masters. The main reason for doing it is to allow prometheus scraping metrics from various kubemark master components, e.g. kubelet. Ref. kubernetes/perf-tests#503
…o-1.11 Automated cherry pick of kubernetes#76656: Switch to instance-level update APIs for Azure VMSS loadbalancer operations
…of-#76773-upstream-release-1.11 Automated cherry pick of kubernetes#76773: Create the "internal" firewall rule for kubemark master.
Kubernetes official release v1.11.10
rjaini
requested review from
honcao,
vikasnav,
Bhuvaneswari-Santharam,
jadarsie and
deaborch
jadarsie
approved these changes
May 6, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Code changes from upstream 1.11.10
We have another code changes seperately to update Compute API version. This code changes is purely upstream code changes.