Skip to content
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

Closed
wants to merge 230 commits into from
Closed

Release 1.7 #1228

wants to merge 230 commits into from

Conversation

mskanth972
Copy link
Contributor

Is this a bug fix or adding new feature?

What is this PR about? / Why do we need it?

What testing is done?

Ashley-wenyizha and others added 30 commits June 21, 2022 18:43
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-1.4 : post-release files updated
Post release update to v1.4 branch (v1.4.3)
jsafrane and others added 21 commits November 9, 2023 10:43
(cherry picked from commit 7ba7628)
Cherry Picked commits for the new release v1.7.1
The SC manifest contained a deprecated ApiVersion, updated the same.
Cherry picked commits for release v1.7.2
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)
@mskanth972 mskanth972 closed this Jan 3, 2024
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 3, 2024
@k8s-ci-robot
Copy link
Contributor

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.

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot
Copy link
Contributor

@mskanth972: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-aws-efs-csi-driver-unit d31495d link true /test pull-aws-efs-csi-driver-unit
pull-aws-efs-csi-driver-verify d31495d link true /test pull-aws-efs-csi-driver-verify
pull-aws-efs-csi-driver-e2e d31495d link true /test pull-aws-efs-csi-driver-e2e
pull-aws-efs-csi-driver-external-test-eks d31495d link true /test pull-aws-efs-csi-driver-external-test-eks

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.

@k8s-ci-robot k8s-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.