[BUG]: CSM Authorization CRD in the CSM Operator doesn't read custom configurations

[atye]

Bug Description

https://github.com/dell/csm-operator/blob/main/samples/authorization/csm_authorization_proxy_server.yaml

The envs and images need to be read from the manifest used to create the CSM Authorization CRD. Most of the settings will always be at the default setting. Images need unique keys in the manifest too.

Logs

NA

Screenshots

No response

Additional Environment Information

No response

Steps to Reproduce

Deploy the Authorization CSM with the Operator with a non-default image.
See that the default image is used in the resulting deployments.

Expected Behavior

Specified image is used in the deployments.

CSM Driver(s)

CSI Drivers that support Authorization

Installation Type

No response

Container Storage Modules Enabled

No response

Container Orchestrator

Kubernetes 1.24

Operating System

RHEL 8.4

[csmbot]

@atye: Thank you for submitting this issue!

The issue is currently awaiting triage. Please make sure you have given us as much context as possible.

If the maintainers determine this is a relevant issue, they will remove the needs-triage label and assign an appropriate priority label.

---

We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at [email protected].