[BUG]: CSM deployment minimal file - pulling from quay after updating the image registry #1633
Assignees
Labels
needs-triage
Issue requires triage.
type/bug
Something isn't working. This is the default label associated with a bug issue.
Comments
anurajpd
added
needs-triage
|
@anurajpd: 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 respond appropriately. We want your feedback! If you have any questions or suggestions regarding our contributing process/workflow, please reach out to us at [email protected]. |
|
@anurajpd can you share your sample YAML ? Because "it works for me with csi-powerflex". |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
CSM deployment minimal file - pulling from quay after updating the image registry
Logs
CSM deployment minimal file - pulling from quay after updating the image registry
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
deploy CSM using minimal file and update the image registry
Expected Behavior
image should be pulled from local registry
CSM Driver(s)
CSM 1.12 PowerMax
Installation Type
CSM Operator
Container Storage Modules Enabled
No response
Container Orchestrator
OpenShift 4.17
Operating System
CoreOS
The text was updated successfully, but these errors were encountered: