Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #32919 from janetkuo/1.3-skip-rollingupdate-old-ku…
…bectl Automatic merge from submit-queue Skip kubectl rolling-update test for client older than 1.4 <!-- Thanks for sending a pull request! Here are some tips for you: 1. If this is your first time, read our contributor guidelines https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md and developer guide https://github.com/kubernetes/kubernetes/blob/master/docs/devel/development.md 2. If you want *faster* PR reviews, read how: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/faster_reviews.md 3. Follow the instructions for writing a release note: https://github.com/kubernetes/kubernetes/blob/master/docs/devel/pull-requests.md#release-notes --> **What this PR does / why we need it**: Fixing upgrade test kubernetes-e2e-gke-1.4-1.3-gci-kubectl-skew Supersedes #32890; garbage collector was introduced in 1.4 which breaks kubectl rolling-update with kubectl <1.4; skip this in 1.3 test to make it passing kubernetes-e2e-gke-1.4-1.3-gci-kubectl-skew **Which issue this PR fixes** *(optional, in `fixes #<issue number>(, #<issue_number>, ...)` format, will close that issue when PR gets merged)*: fixes #32706 **Special notes for your reviewer**: **Release note**: <!-- Steps to write your release note: 1. Use the release-note-* labels to set the release note state (if you have access) 2. Enter your extended release note in the below block; leaving it blank means using the PR title as the release note. If no release note is required, just write `NONE`. --> ```release-note ``` Garbage collector was introduced in v1.4, which caused kubectl rolling-update with kubectl version < 1.4 to fail. This is cherrypicked into 1.3 merely for fixing test failures on kubernetes-e2e-gke-1.4-1.3-gci-kubectl-skew
- Loading branch information