Bug 1913289 - Rebase AWS EBS CSI driver for 4.7
Summary: Rebase AWS EBS CSI driver for 4.7
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Storage
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.0
Assignee: Jan Safranek
QA Contact: Qin Ping
Depends On:
TreeView+ depends on / blocked
Reported: 2021-01-06 13:09 UTC by Jan Safranek
Modified: 2022-01-25 10:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
AWS EBS CSI driver shipped as part of OCP was upgraded to version 0.8.0. The most notable new feature is support for gp3 volume type.
Clone Of:
Last Closed: 2021-02-24 15:50:26 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift aws-ebs-csi-driver pull 176 0 None closed Bug 1913289: Rebase to v0.8.0 for OCP 4.7 2021-01-29 12:43:05 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:50:43 UTC

Description Jan Safranek 2021-01-06 13:09:04 UTC
Upstream has released v0.8.0 recently and we should ship it in OCP 4.7.

Comment 1 Jan Safranek 2021-01-06 13:12:28 UTC
Upstream changelog: https://github.com/kubernetes-sigs/aws-ebs-csi-driver/blob/master/CHANGELOG-0.x.md
The main change is support for gp3 volumes, which is even default when nothing is set in StorageClass. Our operator creates "gp2-csi" StorageClass with "type: gp2", so users should not see any change.

Comment 3 Qin Ping 2021-01-11 07:49:25 UTC
Did a regression test of aws ebs csi driver, all passed.

Verified with: 4.7.0-0.nightly-2021-01-10-070949

Comment 6 errata-xmlrpc 2021-02-24 15:50:26 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.