Make sense. I have no other questions.
DanHua Wang <[email protected]> 于2026年3月30日周一 16:18写道： > > Hi Rory, > > Thank you for your feedback. To address your questions: > > 1. I haven’t seen a requirement for an mcp-server helm chart at this time. > 2. Regarding your second point, gravitino-iceberg-rest-server and > gravitino-lance-rest-server are intended for standalone deployments. While > the main Gravitino chart includes auxiliary service deployments for these > components, using separate charts for standalone use cases provides better > clarity and prevents the configurations from becoming overly complex. > > Best Regards, > > Danhua Wang > > On Mon, Mar 30, 2026 at 3:14 PM roryqi <[email protected]> wrote: > > > OK for me. > > > > Two questions: > > 1. Do we need `mcp-server` helm chart, too? > > 2. Could we have a helm chart to install different Docker images? > > > > Minghuang Li <[email protected]> 于2026年3月30日周一 15:03写道： > > > > > > I totally agree. > > > > > > As Jerry mentioned, this will significantly improve the user experience > > by making the charts much easier to consume. > > > > > > Thanks for proposing this, Danhua. > > > > > > Best, > > > Minghuang Li > > > > > > On 2026/03/30 03:06:23 DanHua Wang wrote: > > > > Hi everyone, > > > > > > > > As we begin publishing charts starting with version 1.3.0, I would > > like to > > > > propose the creation of the following docker hub repositories for chart > > > > releases: > > > > > > > > - apache/gravitino-helm > > > > - apache/gravitino-iceberg-rest-server-helm > > > > - apache/gravitino-lance-rest-server-helm > > > > > > > > You can find more details regarding this proposal here: > > > > https://github.com/apache/gravitino/pull/10515. > > > > > > > > Please let me know if you have any feedback or if you would suggest > > > > alternative naming conventions for these repositories. > > > > > > > > -- > > > > Danhua Wang > > > > Best Regards > > > > > >
