RFC: OLMv1 support - replace OLM dependency model with operator-managed ClusterExtensions

[maleck13]

Summary

OLMv1 removes automatic dependency installation. The Kuadrant operator currently relies on OLMv0 dependency model to automatically install Authorino, Limitador, and DNS operators when a user installs Kuadrant via a single Subscription.

With OLMv1, each operator must be installed as a separate ClusterExtension by the cluster admin, requiring ~20+ resources to install the full Kuadrant stack manually.

[eguzki]

With OLMv1, each operator must be installed as a separate ClusterExtension by the cluster admin, requiring ~20+ resources to install the full Kuadrant stack manually.

I am not familiar with ClusterExtension. After a quick reading, it looks like ClusterExtension replaces the old Subscription API. Then, to install the full Kuadrant stack manually, 5 ClusterExtension objects (5 operators) are required, namely kuadrant-operator, dns-operator, limitador-operator, authorino-operator, and mcp-gateway-operator. So, what are those 20+ resources?

[maleck13]

The SA , RBAC and RBAC bindings have to be created separately now it seems. I am still investigating

See https://raw.githubusercontent.com/operator-framework/operator-controller/main/config/samples/olm_v1_clusterextension.yaml

https://operator-framework.github.io/operator-controller/getting-started/olmv1_getting_started/