-
Bug
-
Resolution: Done-Errata
-
Major
-
4.15.z
Description of problem:
The customer uses Azure File CSI driver and without this they cannot make use of the Azure Workload Identity work which was one of the banner features of OCP 4.14. This feature is currently available in 4.16, however it will take the customer 3-6 months to validate 4.16 and start its rollout putting their plans to complete a large migration to Azure by end of 2024 at risk. Could you please backport either the 1.29.3 feature for Azure Workload Idenity or rebase our Azure File CSI driver in 4.14 and 4.15 to at least 1.29.3 which includes the desired feature.
Version-Release number of selected component (if applicable):
azure-file-csi-driver in 4.14 and 4.15 - In 4.14, azure-file-csi-driver is version 1.28.1 - In 4.15, azure-file-csi-driver is version 1.29.2
How reproducible:
Always
Steps to Reproduce:
1. Install ocp 4.14 with Azure Workload Managed Identity 2. Try to configure Managed Workload Identiy with Azure CSI file https://github.com/kubernetes-sigs/azurefile-csi-driver/blob/master/docs/workload-identity-static-pv-mount.md
Actual results:
Is not usable
Expected results:
Azure Workload Identity should be manage with Azure File CSi as part of the whole feature
Additional info:
- clones
-
OCPBUGS-32785 Azure Workload Identity in static PVs did not work for CSI-File
- Closed
- depends on
-
OCPBUGS-32785 Azure Workload Identity in static PVs did not work for CSI-File
- Closed
- is depended on by
-
OCPBUGS-33039 [4.14] Azure Workload Identity in static PVs did not work for CSI-File
- Closed
- links to
-
RHBA-2024:2773 OpenShift Container Platform 4.15.z bug fix update
(1 links to)