Release 1.12 #79970
Closed
Release 1.12 #79970
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
…le controller does not run in the tests
…nce group deletion
Update to go1.10.8
…68-upstream-release-1.12 Automated cherry pick of #73268 upstream release 1.12
…-release-1.12 Automated cherry pick of #69700: Updated Regional PD failover test to use node taints instead
…97-upstream-release-1.12 Automated cherry pick of #73097 upstream release 1.12
- add incremental scheduling cycle - instead of set a flag on move reqeust, we cache current scheduling cycle in moveRequestCycle - when unschedulable pods are added back, compare its cycle with moveRequestCycle to decide whether it should be added into active queue or not
expected is the existing + 1 this is fixed on master branch in PR #73440. as the test has been moved from scheduling to apimachinery, and many other changes, cherrypick won't work, hence apply the same fix on master branch directly in this release branch.
…upstream-release-1.12 Automated cherry pick of #73309: Should move all unscheduable pods when we received move request to active queue
…tPods is enabled.
…58-upstream-release-1.12 Automated cherry pick of #72558: add goroutine to move unschedulablepods to activeq regularly 1.12
`elbv2.AddTags` doesn't seem to support assigning the same set of tags to multiple resources at once leading to the following error: Error adding tags after modifying load balancer targets: "ValidationError: Only one resource can be tagged at a time" This can happen when using AWS NLB with multiple listeners pointing to different node ports. When k8s creates a NLB it creates a target group per listener along with installing security group ingress rules allowing the traffic to reach the k8s nodes. Unfortunately if those target groups are not tagged, k8s will not manage them, thinking it is not the owner. This small changes assigns tags one resource at a time instead of batching them as before. Signed-off-by: Brice Figureau <brice@daysofwonder.com>
…-upstream-release-1.12 Automated cherry pick of #72455: e2e-node-tests: fix path to system specs
…2-upstream-release-1.12 Automated cherry pick of #73482: Always select the in-memory group/version as a target when
…73721-upstream-release-1.12 Automated cherry pick of #73721: fix mac filtering in vsphere cloud provider
k8s-ci-robot
added
area/e2e-test-framework
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: peterningning The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA. It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
k8s-ci-robot
added
the
cncf-cla: no
|
/close |
|
@andyzhangx: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: