Description of problem (please be detailed as possible and provide log snippets): From OCP 4.12 onwards, gp2 Sc is eliminated. All ocurances should be replaced with gp2-csi. Version of all relevant components (if applicable): Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
I am not sure if I have any exact doc for this, but in ocp 4.12 which is based on k8s 1.25, The in-tree Amazon EBS storage provisioned is deprecated, Which means the gp2 storageclass is no longer there. I don't have the link to the ocp documentation for this. See the note section here https://docs.amazonaws.cn/en_us/eks/latest/userguide/storage-classes.html#:~:text=the%20Kubernetes%20documentation.-,Note,-The%20in%2Dtree. See the gchat discussion regarding this here https://chat.google.com/room/AAAAREGEba8/xylQ-c-y9oA. Tagging Nitin if he wants to add something here
Hello, Petr. We are determining the IOPS speed (fast, slow) based on a few parameters, one of which is the name. There is only one change in the controllers, we added the gp2-csi to the list of storageclasses. The other changes are mostly test changes.
What I meant is if we have anywhere in our ODF doc mentioned the GP2 storageclass? And if so, we need to change it also in our documentation. Do we have gith repository for ODF Documentation, and where I can check this and git grep gp2 if we are mentioning it somewhere?
I got information from Olive that we have occurrences in our docs to gp2 or gp3 SCs. Hence opened this documentation bug: https://bugzilla.redhat.com/show_bug.cgi?id=2140667
Yes Petr, it's safe to mark as verified.
Based on discussion, marking as verified.