Jan Schlicht

Let's update this to use a recent version of `flink-demo` that uses KUDO's dependency feature. With that, most setup steps aren't necessary anymore, the `flink-demo` operator will take care of...

One thing might be a problem though: We already install O/OVs for a lot of operators as part of the test setup: https://github.com/kudobuilder/operators/blob/master/kuttl-test.yaml. We should run this test in a...

Just came across this again while trying to convert more tests to use `kuttl` in https://github.com/mesosphere/kudo-cassandra-operator. This feature is a prerequisite for this as many tests need to assert that...

This is an interesting idea, providing additional ways of triggering plans sounds great! Not sure though how that could look like. KUDO follows the standard Kubernetes model of a controller...

Some high level comments based on the description, didn't look into the code yet: 1) I think that parent repo entries _shouldn't_ take precedence. Repos including other repos should be...

Okay, your example is exactly what I meant. If repo A includes repo B and provides its custom version of an operator that's already in repo B, then the operator...

Yes, that should be enough. Through the Kubernetes API we could check if the KUDO controller pod is running and which version of the image is deployed.