<p>Apache Kafka is available for Kubernetes by Strimzi, and on OpenShift by RedHat(AMQ Stream). RedHat's AMQ stream is based on Strimzi's Kafka Operator.</p>
<p>But when you define a Kafka resource like a broker or topic you start your YAML with something like this</p>
<p><code>apiVersion: kafka.strimzi.io/v1beta1</code></p>
<p>It clearly says beta1, which means it is not production-ready.</p>
<p>Should I use Strimzi's Kafka operator on my Kubernetes/Openshift cluster?
Or is there any other option too?</p>

Sakhawat
<p>I can say that Strimzi is really production-ready. There are already some users using it in production and you can see some of them on the website (<a href="https://strimzi.io/" rel="nofollow noreferrer">https://strimzi.io/</a>) and all of them in the ADOPTERS file here <a href="https://github.com/strimzi/strimzi-kafka-operator/blob/master/ADOPTERS.md" rel="nofollow noreferrer">https://github.com/strimzi/strimzi-kafka-operator/blob/master/ADOPTERS.md</a></p>
<p>Sometimes happens, even in the Kubernetes land, that an API version is still beta while really stable.
We have an actual plan to finally move to CRD v1 and you can read about this in this Strimzi proposal got accepted and to be developed.</p>
<p><a href="https://github.com/strimzi/proposals/blob/master/009-crd-v1-roadmap.md" rel="nofollow noreferrer">https://github.com/strimzi/proposals/blob/master/009-crd-v1-roadmap.md</a></p>
<p>Right now we are at 0.20.0 and we plan to have a kind of gate release on January 2021 and a final move to v1 in April.</p>
<p>Anyway, again, there is no need to wait for that time I can confirm that Strimzi is production ready.</p>
