adityamparikh opened a new issue, #229: URL: https://github.com/apache/solr-mcp/issues/229
### Motivation The Solr Operator manages Solr infrastructure on Kubernetes and stops at the Solr HTTP API; solr-mcp starts at the Solr HTTP API. Bridging them today is manual: read service names off the `SolrCloud` CR, decode the bootstrap secret, and switch between `kubectl` and the Collections API for anything cluster-wide. ### Scope boundary (applies to every child issue) solr-mcp does **not** call the Kubernetes API and gets no tools that edit Kubernetes objects. All infrastructure facts are in `SolrCloud.status`; all infrastructure changes are CR edits. Keeping a Kubernetes client out of the process keeps the threat model in #160 unchanged. Cluster procedures live in a companion agent skill, not here. ### Children - [ ] #222 TLS: trust a custom CA; document existing basic-auth properties - [ ] #223 `get-cluster-status` and `list-configsets` - [ ] #224 Backup and restore tools - [ ] #159 Alias tools (open PR) - [ ] #226 Prompts `plan-reindex` and `diagnose-cluster` - [ ] #225 Amend server instructions with the infrastructure boundary - [ ] #227 Helm chart - [ ] #228 CI: `kind` smoke test against a real Solr Operator ### Sequencing ``` #222 ───────────┐ #174 (release) ──┼──► #227 chart ──► #228 kind CI #159 aliases ────┼──► #226 prompts #223 ────────────┤ #224 ────────────┘ ``` #222, #223, #224 and #225 have no dependencies. ### Explicitly out of scope Multi-cluster; any Kubernetes API call; `delete-collection`; `delete-backup`; a ZooKeeper-addressed client (would replace `HttpJdkSolrClient` and its native-image setup — separate discussion if ever); tool grouping/filtering. ### Companion agent skill A capability-detecting `solr-on-kubernetes` agent skill covers the Kubernetes-side procedures this server deliberately excludes (scaling, rolling upgrades, TLS/auth CR config, incident triage, backup/restore CR scheduling). It works whether or not any of the tools above are present, falling back to `kubectl exec` + `curl` against the pod when a given solr-mcp tool is missing. Prototyped separately; not part of this repo. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
