operator-framework
Supporting custom resources in the CSV
Feature Request
Is your feature request related to a problem? Please describe. We are considering the use of OLM to manage both kubernetes operators and crossplane packages with the same "package manager". But it seems that CSVs currently do no support installing only custom resources (like crossplane XRDs and compositions).
Describe the solution you'd like Ability to support arbitrary custom resources (without deployment) in a CSV.
Hi @philippart,
Thanks for making this request! This is an often requested feature, but the current OLM architecture is too opinionated to handle arbitrary resources without lots of thought and care. However, the OLM maintainers are in the midst of a major architecture change, and we have some early alpha bundle formats and controller implementations that enable this sort of thing.
The rukpak project specifies a design for extensible management of bundle content. We have defined a plain bundle format that is literally a static pile of Kubernetes YAMLs, and we have a plain provisioner that can unpack and apply arbitrary resources.
In addition we also have the operator-controller project, which sits on top of rukpak, knows about operator catalogs, and can manage operator lifecycle in the context of upgrades and dependency resolution.
If you're interested in learning more, I'd encourage you to read the rukpak docs and the OLMv1 roadmap. The community also meets Tuesdays at 11 AM Eastern time if you're interested in attending our WG meetings, where we discuss current progress/upcoming work and answer any questions folks have. (a bunch of helpful info here: https://github.com/operator-framework/community#operator-lifecycle-manager-working-group)
@joelanford thank you for the quick feedback. I'll definitely have a look at these projects!