Hi Thamanna,

Plenty of production deployments are managed by Openstack-Helm (often indirectly). Usually users have their downstream with some customizations and it is common practice to utilize additional orchestration tools. AT&T has been behind the project from its very beginning, also Vexxhost is using it with their Atmosphere, Mirantis also has their downstream based on Openstack-Helm with their custom operator (now open source), AFAIK ResetData (Australian cloud company) is also using Openstack-Helm with Terraform, Rackspace has been actively using (with ArgoCD if I remember correctly) and contributing to the project recently.


On Mon, Mar 3, 2025 at 2:30 AM Thamanna Farhath <thamanna.f@zybisys.com> wrote:

Hello OpenStack Community,

I hope this email finds you well.

I am currently exploring OpenStack-Helm for deploying OpenStack and would like to understand its adoption in live production environments. Specifically, I am interested in knowing if any cloud providers have successfully deployed and are operating OpenStack using OpenStack-Helm in production.

If there are any case studies, references, or experiences shared by operators who have implemented this deployment method, I would greatly appreciate any insights or guidance.

Looking forward to your valuable input.






Disclaimer :  The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender.

 

E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."




--
Best regards,
Kozhukalov Vladimir