block storage is still used in sas-rabbitmq-server when V4_CFG_MANAGE_STORAGE is false #641
Description
Viya4 Deployment Version Details
We noticed that viya4-deployment set storageClassName to io2-vol-mq for RabbitMQ, even though we have V4_CFG_MANAGE_STORAGE set to false.
According to the documentation (viya4-deployment-main/docs/CONFIG-VARS.md), when V4_CFG_MANAGE_STORAGE is set to false, the deployment should NOT use block storage io2-vol-mq for RabbitMQ:
When V4_CFG_MANAGE_STORAGE is set to true, viya4-deployment uses the EBS CSI driver to create two elastic block storage based storage classes with the default names of io2-vol-mq and io2-vol-pg. The volume type for both storage classes defaults to io2. For EKS clusters, RabbitMQ makes PVC requests to create block storage persistent volumes using the io2-vol-mq storage class while Crunchy Postgres makes PVC requests to create block storage persistent volumes using the io2-vol-pg storage class. Viya4-deployment also creates the sas storage class using the csi-driver-nfs Helm chart. If a jump server is used, viya4-deployment uses that server to create the folders for the astores, bin, data and homes RWX Filestore NFS paths that are outlined below in the RWX Filestore section.
Ansible Variable File Details
No response
Steps to Reproduce
Set V4_CFG_MANAGE_STORAGE to false in ansible-vars.yaml and build with viya4-deployment ansible playbook.
Expected Behavior
storageClassName for sas-rabbitmq-server should be sas
Actual Behavior
storageClassName for sas-rabbitmq-server is io2-vol-mq
Additional Context
No response
References
No response
Code of Conduct
- I agree to follow this project's Code of Conduct