-
Notifications
You must be signed in to change notification settings - Fork 544
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 1.7 #1228
Release 1.7 #1228
Conversation
Pre-release of v1.4.0
….4.0 Post release branch update1.4.0
Pre-release of v1.4.1
Post release PR of v1.4.1
revise helm chart version
Merge master into release-1.4 branch for release v1.4.1
Revert "Merge master to release-1.4 branch for release v1.4.1"
Due to improper index calculation, an incorrectly formatted language tag can cause Parse to panic via an out of bounds read. If Parse is used to process untrusted user inputs, this may be used as a vector for a denial of service attack. Source: https://deps.dev/advisory/OSV/GO-2021-0113 Updated using following commands: go mod why -m golang.org/x/text go get -u k8s.io/client-go/rest golang.org/x/net/http2 golang.org/x/net/idna golang.org/x/text/secure/bidirule go mod tidy && go mod vendor
Log this behavior, return nil but do not fail
Release-v1.4.2 commits cherry pick
Pre-release of v1.4.2
Release-1.4 : post-release files updated
Release-1.4.3: Pre-release updates
Signed-off-by: dschunack <[email protected]>
Add #743 to changelog
Post release update to v1.4 branch (v1.4.3)
(cherry picked from commit 7ba7628)
(cherry picked from commit 79bf1cf)
Cherry Picked commits for the new release v1.7.1
Pre-release for v1.7.1
Post-release PR for v1.7.1
The SC manifest contained a deprecated ApiVersion, updated the same.
Cherry picked commits for release v1.7.2
Pre-release for v1.7.2
Post-release PR for v1.7.2
(cherry picked from commit dadf1aa)
(cherry picked from commit 78be699)
DescribeAccessPointsWithContext call returns only 100 results by default. Since this is used for discovering used GIDs on access points we must not allow listing only a subset of access points. This is because gid allocator relies on this call to filter out used GIDs and getting next *free* GID. If we don't make sure to list every access point it will cause allocator to pick GID that might already be taken. (cherry picked from commit 16557ce)
PR needs rebase. 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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mskanth972 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@mskanth972: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
Is this a bug fix or adding new feature?
What is this PR about? / Why do we need it?
What testing is done?