The operator's config.yaml file is not a config file in the usual sense. It maps GVK to an ansible role or playbook. We would never put other runtime settings in it such as debug level, what port to run the proxy on, etc. This file is how you compose an operator, and changing its contents could leave you with a fundamentally different operator.
As such, I propose changing the name to avoid confusion. Since the file is a list of GVKs to watch, combined with info about what to do for that GVK, I suggest renaming it to watches.yaml.
The operator's
config.yaml
file is not a config file in the usual sense. It maps GVK to an ansible role or playbook. We would never put other runtime settings in it such as debug level, what port to run the proxy on, etc. This file is how you compose an operator, and changing its contents could leave you with a fundamentally different operator.As such, I propose changing the name to avoid confusion. Since the file is a list of GVKs to watch, combined with info about what to do for that GVK, I suggest renaming it to
watches.yaml
.