Cannot start feast go server with helm

Expected Behavior

A go feature-server can be running.

Current Behavior

Only a python feature-server is running

INFO: Started server process [1] INFO: Waiting for application startup. INFO: Application startup complete. INFO: Uvicorn running on http://0.0.0.0:6566 (Press CTRL+C to quit)

Steps to reproduce

1. setting go_feature_serving: True in a feature_store.yaml
2. following this guide to install feature-server with helm.

Specifications

• Version:
• Platform:
• Subsystem:

Possible Solution

Adding a more clear guide about how to start go feature-server in readme.

Same issue here, looking forward to solutions : ((

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Have you found a solution? Encountered an issue myself. Go feature serving doesn't work for me with helm or just by using CLI with go_feature_serving: True in feature_store.yaml . If someone found a solution - please comment it here.

I am fairly certain that Feast no longer supports Go Servers and they just haven't updated the documentation - the source code doesnt allow for grpc type servers, even if you explicitly set it as such. It seems like an oversight on the documentation/code sync. Super disappointing as it is something I intended to use as well - especially since the docs point to it.

@TheFallen312 @peter-resnick heya, we've recently given this another look as I've been working through issue backlogs & I can confirm that as of today (we're actually conversing on it in our Slack), there's a good amount of code in-repo for go feature server, but it currently is not executable due to falling out of maintenance some time ago. With new maintainers & revived interest in place, we're looking at a short-term update to docs to better inform users as to current condition, but I also hope long-term I to spur some discussions & activity for bringing the go server back into the fold.

FWIW, a few weeks ago we had someone join our community call & share that their company had been working with it out of a fork & would look to contribute back, so we're also hopeful we'll maybe see a jump start contribution in that direction soon.

Going to close this issue and use your newly created 3998 as a tracker given the bettter amount of info provided (and honestly, just time relevance). Thanks for opening, we'll bring updates there as we have them.