You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We automatically camel-case module name, but if the module name has some abbreviation – we get ugly things, like getting nodeLocalDns, instead of 'nodeLocalDNS`.
Sometimes we need to know module namespace, but we don't have centralized mapping.
It would be generally better if we will pass namespace to helm install, at least:
we will have namespaces in helm list,
we will be able to use Release.Namespace, instead of hardcoding namespace name into each template.
Add module.yaml to each module, and make it required. It should contain, at least, name (camel-cased), namespace and order, all required.
Use name (camel-cased) from module.yaml when generating helm values, and in all other places (list of enabled modules, logs, etc).
Add the automagic global variable with module-to-namespace mapping.
Extra logic:
When namespace of the module is changed – perhaps the module should be uninstalled first (as far I remember helm doesn't allow changing namespace for the installed release).
When module name changes, for addon-operator it should be similar to one module gone, and a new one added.
The text was updated successfully, but these errors were encountered:
Problems:
nodeLocalDns
, instead of 'nodeLocalDNS`.helm install
, at least:helm list
,Release.Namespace
, instead of hardcoding namespace name into each template.Proposal:
Extra logic:
The text was updated successfully, but these errors were encountered: