Hi @teovillanueva , happy to know you consider using Qovery . I respond inline.
Yes, you can deploy your environments into separate clusters. It’s a good pattern if you want to isolate your production from your staging/dev environments.
To have multiple clusters, it’s as simple as:
Getting into your organization settings
Add a new cluster
When you create a new environment, you will have the ability to deploy it into the cluster you want.
Same as above, with the difference that you need to create a “Deployment rule” to indicate where you need to create the new environment based on your git branch name.
Can you clarify your question? What do you mean by GitHub deployment environments? Qovery integrates to your git and will deploy automatically (configurable) every change that you make on your Git repository.
We plan to support Preview URL in your Pull Request for march 2022 (this month). cc @Alessandro_Carrano@a_carrano@Florian_Lepont
You can rollback your application. Check this out here.
Unfortunately, no, but happy to have your contribution with a tutorial on how-to You can drop the qovery namespace in your Kubernetes cluster and remove your cloud credentials, and you will be free of Qovery while keeping your infrastructure running. Plus, we give you access to all the generated Terraform files.
You can follow John’s video to set up your Qovery account. Happy to help you out via this forum if you need any help.
We do support Redis out of the box, so you don’t need to install it yourself. However, we do not support Kafka but there is no problem for you to install it on your Kubernetes cluster via helm (we have several customers doing that with zero issues).
, happy to know you consider using Qovery 
. I respond inline.