As reshapr uses descriptive paradigms for its core components like Configuration, Secret, Exposition but also CustomTools and Prompts, it's fairly easy to see the analogy with the GitOps approach.
All the elements of a comprehensive MCP Server configuration could be expressed using YAML assets that can be stored in a versioning system like Git, and we could imagine having Reshapr Custom Resources in Kubernetes that would allow automatic provisioning of MCP endpoints just from versioned files.
The proposition here is to develop a Kubernetes Operator that allows managing the lifecycle of Reshapr Custom Resources in a target control plane (think about creating, syncing, removing stuff in the control plane based on Kubernetes CR)
What do you think? Any thoughts?
As reshapr uses descriptive paradigms for its core components like
Configuration,Secret,Expositionbut alsoCustomToolsandPrompts, it's fairly easy to see the analogy with the GitOps approach.All the elements of a comprehensive MCP Server configuration could be expressed using YAML assets that can be stored in a versioning system like Git, and we could imagine having Reshapr
Custom Resourcesin Kubernetes that would allow automatic provisioning of MCP endpoints just from versioned files.The proposition here is to develop a Kubernetes Operator that allows managing the lifecycle of Reshapr Custom Resources in a target control plane (think about creating, syncing, removing stuff in the control plane based on Kubernetes CR)
What do you think? Any thoughts?