Hi Team,
We are very interested in adopting Conductor OSS for our critical project. However, we noticed that there is no official deployment guide specifically for Kubernetes/OpenShift. While we can create the YAML files ourselves, it would be ideal to have guidance directly from the Conductor product team or maintainers.
We appreciate any inputs or recommendations you can share.
Hi Zoheb, Thanks you for your note. We at Orkes are actively looking into writing a guide and we will get back to you on this in a few days with more details and guidance.
Cheers
Hey Zoheb — I’m an engineer working primarily on the Conductor OSS codebase and I wanted to follow up on this directly.
I just put together an official Kubernetes/OpenShift deployment guide and tested it end-to-end on a bare Linux box, no cloud magic. This “getting started” repo is a new addition to the conductor-oss world and I’ll be adding more guides like this one over time.
The guide uses Postgres as the starting point since it covers both persistence and queuing in one service, but it also walks through Redis, MySQL, and Cassandra configs if that’s what your stack calls for. Manifests and full guide here: getting-started/kubernetes at main · conductor-oss/getting-started · GitHub
Happy to answer questions.
And if you have any trouble getting started, please file it right in the “getting started” repo. Thanks!
Hi Naomi,
Really appreciate you reaching out and sharing the new guide. I’ll walk through the Kubernetes/OpenShift setup and test it against my environment. The Postgres-first approach makes sense, and it’s great that you’ve included Redis/MySQL/Cassandra configs as well. I believe Elasticsearch is no longer required if we are using PostgreSQL?
If anything comes up, I’ll file it in the repo. Happy to share feedback as you expand the getting-started series.
Correct, ElasticSearch is not required – in fact it’s not recommended.
Thanks for circling back!