-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE]: CSI-PowerMax - Mount credentials secret to the reverse-proxy (Customer Ask) #1614
Labels
area/csi-powermax
Issue pertains to the CSI Driver for Dell EMC PowerMax
type/feature
A feature. This label is applied to a feature issues.
Milestone
Comments
rajkumar-palani
added
type/feature
A feature. This label is applied to a feature issues.
area/csi-powermax
Issue pertains to the CSI Driver for Dell EMC PowerMax
labels
Nov 26, 2024
jooseppi-luna
changed the title
[FEATURE]: Mount credentials secret to the reverse-proxy and not get the reverse-proxy pulling it from k8s API
[FEATURE]: CSI-PowerMax - Mount credentials secret to the reverse-proxy (Customer Ask)
Dec 10, 2024
9 tasks
10 tasks
This was referenced Jan 14, 2025
Merged
12 tasks
8 tasks
5 tasks
3 tasks
13 tasks
8 tasks
9 tasks
8 tasks
This was referenced Feb 4, 2025
9 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/csi-powermax
Issue pertains to the CSI Driver for Dell EMC PowerMax
type/feature
A feature. This label is applied to a feature issues.
Feature – Today, the csi-reverseproxy accesses Unisphere credentials by using a K8s api call to read them from a configmap, unlike all the other drivers, which mount a secret as a volume in the driver pod.
This feature brings the reverseproxy in line with all the other drivers – the configmap will be converted to a secret and mounted to the controller pod as a volume. The
Benefit hypothesis – Moving to a mounted secret will make csi-powermax consistent with other drivers, and will allow us to integrate with Hashicorp Vault, which uses a sidecar injector that can inject secrets directly into the pod, not into the k8s secret object (cf. email).
The text was updated successfully, but these errors were encountered: