adityamparikh opened a new issue, #228: URL: https://github.com/apache/solr-mcp/issues/228
### Current state (verified) CI uses Testcontainers and `compose.yaml`. Nothing exercises operator naming, secrets, or TLS. ### Scope `.github/workflows/kind-smoke.yml`, on PRs touching `deploy/**` or `src/main/java/**/config/**`, plus nightly: 1. `kind create cluster` 2. `helm install` cert-manager, zookeeper-operator, solr-operator (pinned minor) 3. `kubectl apply -f deploy/examples/solrcloud-films.yaml` (1 replica, basic auth on, TLS off in v1); wait for `.status.readyReplicas == 1` 4. Build the image with the existing Gradle/Jib task (**verify** task name in `build.gradle.kts`); `kind load docker-image` 5. `helm install solr-mcp deploy/helm/solr-mcp --set solrCloud.name=films --set mcp.security.enabled=false` 6. Port-forward; `tools/list` returns the expected names; `list-collections` succeeds (proves auth wiring); `get-cluster-status` shows one live node (#223) ### Acceptance - [ ] Green on `main`, under ~12 minutes. - [ ] On failure, upload `kubectl get solrcloud -o yaml` and solr-mcp pod logs as artifacts. - [ ] `deploy/examples/solrcloud-films.yaml` committed and linked from the chart docs. ### Depends on #227. Part of the Kubernetes / Solr Operator integration tracking issue. -- 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]
