cshuo opened a new pull request, #20737: URL: https://github.com/apache/hudi/pull/20737
### Describe the issue this Pull Request addresses Part of #20619 and RFC-117 (#20575). This draft builds on #20621. While that PR is open, review the [minikube commit](https://github.com/cshuo/hudi/commit/afc755d8f666cdf12cb44ea3bdb9ea82f1f0ca51) for the changes introduced here. ### Summary and Changelog - Run `./hudi-lakehouse/local-dev/lakehouse.sh up --build` to install MinIO, Hive Metastore, Spark Connect, and Agent Gateway in a dedicated minikube profile. Subsequent runs can reuse local images. Users can also supply registry image tags. - Initialize missing `trips` and `drivers` tables and verify Spark Connect and MCP queries. Check built-in chat separately so MCP stays usable when the LLM is unavailable. - Add status, diagnostics, and lifecycle commands. `down` stops workloads and preserves the namespace and both PVCs. ### Impact Existing Trino and Connect-only development entry points remain available. The shared local-dev teardown now preserves data across restarts. ### Risk Level Low. All 132 lakehouse regression tests passed. Live minikube validation with local images covered MCP joins, an Ollama chat SQL tool call, and MCP queries with the LLM unavailable. Two stop/start cycles preserved both PVCs, an updated fare, a deleted trip, and an empty drivers table. ### Documentation Update The [minikube installation guide](https://github.com/cshuo/hudi/blob/afc755d8f666cdf12cb44ea3bdb9ea82f1f0ca51/hudi-lakehouse/local-dev/INSTALL.md) covers image selection, sample queries, diagnostics, and data retention. ### Contributor's checklist - [ ] Read through the [contributor's guide](https://hudi.apache.org/contribute/how-to-contribute) - [x] Enough context is provided in the sections above - [x] Adequate tests were added if applicable -- 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]
