STOR-2015: Rebase to upstream v2.0.7 for OCP 4.18 #86
Conversation
(cherry picked from commit f6f1091)
(cherry picked from commit 8071588)
Rust and Cargo are required to build efs-utils v2.0.0. I also a TODO to one of our integration tests - now that non-tls mounts are also re-directed to localhost (efs-utils v2), we need a new method of determining whether 'encryptInTransit' is working as expected. (cherry picked from commit f503354)
(cherry picked from commit 5a73a76)
…s2.0.0 Pre-release PRs for v2.0.0
…Rsv2.0 Post-release PR for v2.0.0
Pre-release PR for v2.0.1
…ckerhub to Public ECR
…2.0.1 Post-release PR for v2.0.1 and also changed the Default image from do…
Update CHANGELOG to include 2.x for newer versions.
Update the Helm configuration to use Public ECR image default rather…
Pre-release PR for v2.0.2
Post-release PRs for v2.0.2
…onset (cherry picked from commit 142a464)
(cherry picked from commit 8bf61b7)
…_for_v2.0.3 Cherry pick PR's for v2.0.3
…se-2.0 pre-release PR v2.0.3
post-release PRs for v2.0.3
if env var `FIPS_ENABLED` is set: kubernetes-sigs#1325 . (cherry picked from commit f5581f0)
Signed-off-by: Omer Aplatony <[email protected]> (cherry picked from commit 661b9a1)
(cherry picked from commit ddfc936)
(cherry picked from commit 2de0126)
When reuse access point flag is set to true, there is no point in doing a lot of work that is aimed at preparing the options for the createAccessPoint call (e.g. allocating a GID). We can save quite some time and quite some API calls if the AP with the same clientToken is found. The check for the AP existence has been moved from the CreateAccessPoint function one level up. The controller in this case checks if there is an access point with such client token, if so, it proceeds to return a CreateVolumeResponse. If it is not found, then it follows the usual flow. (cherry picked from commit 58c8272)
(cherry picked from commit d21d258)
…or_2.0.6 Cherrypicks for 2.0.6
….0.6re Pre-release PR for v2.0.6
post-release PR for v2.0.6
Update Go Version
openshift-ci-robot
added
the
jira/valid-reference
|
@dfajmon: This pull request references STOR-2015 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set. 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 openshift-eng/jira-lifecycle-plugin repository. |
Additional changes: - remove .github files - do not overwrite GOARCH in makefile - go mod tidy && go mod vendor
dfajmon
force-pushed
the
rebase-v2.0.7
branch
from
566aff3
to
60e489f
Compare
|
@dfajmon: all tests passed! Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
|
/lgtm |
openshift-ci
bot
added
px-approved
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dfajmon, jsafrane 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 |
openshift-ci
bot
added
the
approved
Issue link:
https://issues.redhat.com/browse/STOR-2015
Diff to upstream v2.0.5:
kubernetes-sigs/aws-efs-csi-driver@v2.0.5...dfajmon:rebase-v2.0.7
Changes between v2.0.5 (OCP 4.17) and v2.0.7 (OCP 4.18):
Full changelogs:
https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/CHANGELOG-2.x.md
@openshift/storage