Description of problem:
Found that upstream has support gp3 as default volume, we can update storageclass gp2-csi
Version-Release number of selected component (if applicable):
Create storageclass gp3csi
Node Log (of failed PODs):
StorageClass Dump (if StorageClass used by PV/PVC):
We could create gp3-csi instead of gp2-csi in the CSI driver operator. It will not be the default one (at least until CSI migration is GA). I'd wait for 4.10 with that, 4.9 is pretty late in dev. process now.
(In reply to Jan Safranek from comment #1)
> We could create gp3-csi instead of gp2-csi in the CSI driver operator. It
> will not be the default one (at least until CSI migration is GA).
I have a second thought about this. We should probably ship both csi-gp3 and csi-gp2, just in case someone depends on csi-gp2.
Verified pass 4.10.0-0.nightly-2021-09-17-053541
Is there any possibility of this being enabled in 4.9? I see internal updates showing previous testing but no confirmation of validity.
It's enabled only in 4.10. Users are free to create their gp3 storage class manually in 4.9, gp3 it's supported there.
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.10.3 security 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.