[Proposal] Add support to OLM bundle format#703
[Proposal] Add support to OLM bundle format#703varshaprasad96 wants to merge 1 commit intocarvel-dev:developfrom
Conversation
This commit intends to add a proposal to introduce support for installing OLM bundles in registry+v1 format to kapp-controller. Signed-off-by: Varsha Prasad Narsing <varshaprasad96@gmail.com>
✅ Deploy Preview for carvel canceled.
|
|
cc: @ncdc |
praveenrewar
left a comment
praveenrewar
left a comment
There was a problem hiding this comment.
Could we also add a desired workflow for users to be able to install operators?
| } | ||
| ``` | ||
|
|
||
| With the help of the following inputs, kapp-controller can then convert the registry+v1 contents into a set of plain kubernetes manifests. |
There was a problem hiding this comment.
I think a little bit more details need to be added on how kapp-controller can convert this into plain Kubernetes manifests.
There was a problem hiding this comment.
@praveenrewar The conversion between OLM's registryV1 to plain k8s manifest is based on a yaml named "ClusterServiceVersion" - CSV (https://olm.operatorframework.io/docs/concepts/crds/clusterserviceversion/). There is a direct 1 on 1 translation - which means that based on the info given specified in a CSV yaml (like deployment spec and permissions) we create individual ClusterRoles, service accounts, Bindings, Deployments etc.
|
@praveenrewar The e2e workflow remains the same as it is now with any other bundle using kapp-ctrl with the introduction of this templating step. With this change, we intend to enable the installation of operators using an OLM specific format. That being said, kapp-ctrl as is can still deploy operators - if it is packaged using Helm chart, or just through a bunch of plain k8s manifests. |
|
@varshaprasad96 , |
3 participants
This commit intends to add a proposal to introduce support for installing OLM bundles in
registry+v1format to kapp-controller.