search

operator-framework / operator-controller

Apache License 2.0
28 stars 47 forks source link

[RFE] Allow installing resources in a namespace different than targetNamespace #958

Closed iblancasa closed 1 week ago

iblancasa commented 1 week ago

We want to create some dashboards for OpenShift in the OpenTelemetry Operator. This is done by creating a ConfigMap in the openshift-config-managed namespace.

Something we tried was to add the ConfigMap directly to the OLM bundle setting the .metadata.namespace but OLM ignores the setting and creates the ConfigMap in the namespace where the operator is installed.

Would it be possible to skip this somehow? Or adding a new feature for this.

joelanford commented 1 week ago

This repository is for OLMv1 only, and we are no longer accepting feature requests for OLMv0.

But this is a known issue in OLMv0 and something we will be addressing in OLMv1. This is a limitation of the registry+v1 bundle format and the assumptions that registry+v1 bundle authors have when they build these bundles. We are not planning to extend the registry+v1 format with new features or behaviors.

Instead, in OLMv1, we are planning to support helm charts as a packaging format. The ClusterExtension API would enable arbitrary objects to be created in arbitrary namespaces based on helm templating.

I'm going to close this as a duplicate of https://github.com/operator-framework/operator-controller/issues/962