Evgeniy

Hello! It will be great - for OpenShift it is the common case:

Possible solution - add labels or annotation to the cloudflow custom resources that point to the instance of Cloudflow (by default we have one instance of custom resource "Cloudflow" named...

Another important issue is the delivery of updates between the test and production Kubernetes clusters. The native way is to move the appropriate docker images and apply a set of...

> (where you keep the configuration files for environments is up to you) Am i right that in this case we need to rebuild all images for every environment?

> the same topic names and other typical resources inside different cloudflow instances. > @jenoOvchi I'm not sure what you mean since kafka topics are a cluster-wide resource, not namespaced?...

> You don't need to rebuild images @jenoOvchi Ok, thanks! We will try.

> @jenoOvchi I mean that it is problematic for a cloudflow app in different environments, ie dev, test etc, to use the same topics. So we need a solution for...

Hi! Are support for init containers is in your plans?

> Yes, it is on the backlog. Ok, thanks.

Hi! Is it any updates for this issue?