Thanks for your PR, but this is not the strategy we are aiming for 1.0 KogitoInfra is meant to bind the Kogito services with third party infra, not creating the infra itself. We just kept Kafka/Infinispan/Keycloak for now for backward compatibility. For Kafka: We create KafkaTopics on already created Kafka instance. For Infinispan: We fetch Infinispan server details and inject it into the service, so it could connect to it For Knative Eventing: We bind a given broker with a Kogito service via SinkBindings and Triggers. For Prometheus: We fetch for the metrics endpoint and create ServiceMonitors to bind then together, no KogitoInfra needed. For Graphana: Users should create their own Graphana instance and the operator would fetch for the /dashboards endpoint, if it's in there, we create GraphanaDashboards to be discovered by the Graphana Operator. We won't create Graphana instances whatsoever. I'd say that we won't merge this PR since it's not the strategy we are aiming. No need of a KogitoInfra implementation for this use case.