-
Feature
-
Resolution: Done
-
Major
-
None
-
None
-
Future Sustainability
-
None
-
0% To Do, 100% In Progress, 0% Done
-
False
-
-
False
-
S
-
None
-
-
-
-
-
-
None
-
None
Feature Overview (aka. Goal Summary)
Update AWS EBS CSI driver operator + AWS EFS CSI driver operator (incl. create-efs-volume) to use AWS SDK v2.
Goals (aka. expected user outcomes)
As AWS is planning to end support for AWS SDK v1 we need to upgrade to use the AWS SDK v2. This is not directly exposed / consumed by customers but will avoid future potential issues as we don't want to use an unsupported SDK.
Requirements (aka. Acceptance Criteria):
EBS & EFS driver operator are using AWS SDK v2
| Deployment considerations | List applicable specific needs (N/A = not applicable) |
| Self-managed, managed, or both | both |
| Classic (standalone cluster) | yes |
| Hosted control planes | yes |
| Multi node, Compact (three node), or Single node (SNO), or all | all |
| Connected / Restricted Network | all |
| Architectures, e.g. x86_x64, ARM (aarch64), IBM Power (ppc64le), and IBM Z (s390x) | non arch specific |
| Operator compatibility | EFS / EBS |
| Backport needed (list applicable versions) | no |
| UI need (e.g. OpenShift Console, dynamic plugin, OCM) | no |
| Other (please specify) | .. |
Out of Scope
Limited to EBS & EFS
Background
AWS will end support of their v1 SDK we need to anticipate it and use v2 instead.
Customer Considerations
There should not be any customer visible change
Documentation Considerations
None
Interoperability Considerations
All OCP deployment types on top of AWS.
