In #159530 (comment), @elastic/kibana-core team went from owning /config/kibana.yml to owning all the files inside /config/.

IMO, this makes sense for consistency in /config/kibana.yml and /config/serverless.yml.

However, I wonder if the project-specific /config/serverless.{projectType}.yml files should be owned by Solutions teams instead, as they shape the behavior of their offering. You may argue that the higher-level /config/serverless.yml also does.

• Should we rethink the ownership of these files?
• What are the best teams to own it?
• Would it be best to automate the validations by writing comprehensive functional tests for Serverless? 😇 💣 🤖

For context: configurations are applied as follows:

1. Kibana reads the settings in /config/serverless.yml.
2. /config/serverless.{projectType}.yml overrides the settings set above.
3. /config/kibana.yml applies any user-level settings to override the above. Although users won't be able to change anything of these files on Serverless (at lest for the MVP).