I also think this is a great idea! I don't remember details of the agent configuration, but I think if the AgentMetadataService is implemented by a gRPC service, most of configuration could be omitted. Is that correct? A quick question, how will propeller discover the configmaps?

the AgentMetadataService is implemented by a gRPC service, most of configuration could be omitted. Is that correct?

yes!

A quick question, how will propeller discover the configmaps?

one possible option is to locate the custom agent configmap objects with some convention (name) or some labels. this should be trivia using k8s API….

And putting this discovering and merging logic to propeller manager, I assume?

yeah the propeller is the place to CRUD K8s objects with the right authn/z anyway. Plus, the security infra in the enterprise environment usually approves the control plane such as propeller to do so and other orgs do not need to worry about the additional set up/approval to enable it.

sounds good, and it minimizes the change to propeller. iirc, propeller is pretty static about configs.

yep