[feature]Whether to consider supporting OLM management operators

[whg517]

Through our investigation of the k8s package management scheme, we conclude that in addition to the simple installation management of k8s by helm, it is more convenient and flexible to develop operator by using the open source OLM specification based on RedHat, or Juju based on Ubuntu. Wondering if the community has any plans to consider supporting it, I would love to have more flexible options on our stack.

When developing an operator based on OLM, you can use the operator-sdk development kit to quickly write operator business logic. kubebuilder encapsulates the client-go logic and provides a large number of flexible calling methods, making the development simple and easy.

Developed operators can publish to the operatorhub to host operator index information, or they can publish their own catalogsource installed locally as they are used.

[ssz1997]

@whg517 Thanks for your feedback. We are using part of the operator-sdk toolkit for development, and it is indeed super helpful in terms of generating crds and stuff. Using Helm for managing operator instead of OLM is mainly because I am more familiar with Helm and don't have enough bandwidth to look into OLM, but I am aware of it and seems like it is a pretty popular choice. Right now there is no plan for it, but will definitely do some more investigation.