contour-operator icon indicating copy to clipboard operation
contour-operator copied to clipboard
verified publisher icon projectcontour

Support Operator Lifecycle Manager to Manage Contour Operator

Open danehans opened this issue 5 years ago • 5 comments

Please describe the problem you have Add support for using Operator Lifecycle Manager to manage the operator.

xref Slack discussion: https://kubernetes.slack.com/archives/C8XRH2R4J/p1603824453388600

danehans avatar Oct 27 '20 19:10 danehans

xref: https://github.com/projectcontour/contour-operator/issues/141 xref: https://github.com/projectcontour/contour-operator/issues/142

danehans avatar Dec 02 '20 03:12 danehans

I'd like to understand more about this - I would rather not tie the operator exclusively to a single management framework. How does OLM help solve migration and update problems?

youngnick avatar Jan 18 '21 22:01 youngnick

@youngnick PTAL at how OLM manages community operators for additional information. A simple example that OLM supports is- user currently runs v1.11.0 and wants to upgrade to v1.14.0. OLM will walk through each upgrade step in the chain on behalf of the user and revert if any step fails. I see OLM as an example implementation for managing the operator. We can include add'l operator management examples as they arise. Thoughts?

danehans avatar Apr 15 '21 16:04 danehans

Ah, I see. So OLM support is just about supplying the CSVs and other metadata about versions somehow?

youngnick avatar Apr 27 '21 04:04 youngnick

@youngnick yes, this repo would include the metadata about Contour Operator in order to ensure that it can be kept running safely in a cluster and to provide information about how updates should be applied as we publish new versions of the operator. This is very similar to traditional software packaging mechanisms, i.e. RPMs. Xref for example.

danehans avatar Jun 03 '21 00:06 danehans