Is an operator a package? And how to manage dependencies?

[pierreozoux]

A package in the sense of RPM package. I think it is and if it is, then as part of the operator community we have to fulfill the following - package manager.

In this issue, I'm especially interested in solving the dependency resolution part.

Say that I want to deploy a Nextcloud instance. This depends on an SQL instance. My Nextcloud operator as to resolve this dependency.

What is the plan around dependency management? Maybe there is already one?

Thanks for your help!

[hasbro17]

@pierreozoux When considering operators as packages that need to be managed(installed, upgraded etc) you might be interested in looking at the Operator Lifecycle Manger (OLM), if you haven't already come across it.

The design philosophy and architecture docs should provide a good overview of how OLM manages operators.

Specifically for dependency resolution OLM allows an operator to specify the APIs that are provided by it as well as what APIs are required by(or depended on) by that operator.

With the operator specifying an API that it depends on via the CSV, OLM will ensure that prerequisite is fulfilled by installing the operator that provides that API.

[pierreozoux]

Thanks for your feedback I'll close here, read and open there if necessary.