-
Task
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
Product / Portfolio Work
-
False
-
-
False
-
2
-
None
-
None
-
Pikachu Sprint 276
In order to support bundle config, we'll need to lift configuration from the ClusterExtension API and pass it to the registry+v1 renderer. We want to make `watchNamespace` a configuration parameter. For this task, we start to prepare the ground for the ClusterExtension config by refactoring the registry+v1 bundle to chart converter to take general configuration in the form of map[string]interface{}, do basic validation and defaulting based on the bundle's install mode support, and configure the renderer appropriately.
We must ensure the following validation is performed depending on the install mode support of bundle:
| All | Single | Own | Multi | default TargetNamespaces option |
|---|---|---|---|---|
| Y | N | N | * | nil |
| Y | Y | N | * | corev1.AllNamespaces |
| Y | N | Y | * | corev1.AllNamespaces |
| N | Y | N | * | no default: error if not given |
| N | Y | Y | * | install-namespace |
| N | N | Y | * | install-namespace |
| N | N | N | * | no default: error bundle is invalid |
A/C:
- converter updated to consume configuration
- converter uses default if no value is given
- converter passes the correct renderer options to the renderer
- unit tested
- Single/-OwnNamespace e2es pass
- is depended on by
-
OPRUN-4091 Add inline config support to ClusterExtension API
-
- Closed
-
- links to