Distributed Headlamp settings #3979
Description
Is your feature request related to a problem? Please describe the impact that the lack of the feature requested is creating.
A common request from our users, like @jda258 , has been to be able to configure certain parts of Headlamp or its plugins in a way that will apply to all users (when running Headlamp as a web service).
For example, if someone is using the AI Assistant, instead of having each client/user set up the AI provider, with the needed keys, endpoint, etc. they should just connect to Headlamp and it should be pre-configured to them.
Describe the solution you'd like
Even if each plugin can implement solutions for distributed configuration however they want, I think that Headlamp should offer plugins a standardized way to read configuration from a cluster (or clusters).
For example, this could be having a specific configmap, in a specific namespace, like "ConfigMap: headlamp-general-config", in a namespace with a specific label like headlamp.dev.settings-general: configmap:headlamp-general-config .
Then a plugin could have its own settings like:
_headlamp.dev.settings-plugin/headlamp-ai-assistant: configmap:headlamp-ai-assistant-settings .
Every time we connect to a cluster, we could check if a namespace has the special label and check for the settings if it does.
When getting the settings via the Headlamp-provided lib, we could have a flag "check-remote = true|false" for allowing the settings to be distributed.
What users will benefit from this feature?
Vendors who deploy Headlamp and need to have centralized settings for Headlamp or its plugins.