Communicating to Feast Kubernetes client

[Al4DIN]

Expected Behavior

Be able to interact and use feast feature server which it's deployed on Kubernetes

Current Behavior

Client class not used anymore on new version of Feast, and RepoConfig only allows 3 modes (local, Aws, and GCP)

Steps to reproduce

Specifications

• Version: 0.31.0
• Platform: Kubernetes 1.26
• Subsystem: Jupyter Notebook on Kubeflow 1.6.1

Possible Solution

Modify the load_repo_config and add the possibility for the on premise mode with communicating to the service associated to Feast-feature-service and to be able to retrieve the feature_store.yaml used (same as local mode)

[davidegavio]

Hello @Al4DIN, any news on this subject?

[tokoko]

@Al4DIN Can you be more specific what you mean here? Are you looking for a way for get_online_features calls to resolve features from a feature server deployed on k8s? Or is it something else?

[Al4DIN]

@davidegavio Hello not really, the only workaround I found is to use the feast lib then port-forward the server so I can access to the UI :(

[Al4DIN]

@tokoko Before on the version 0,6-, we used to have a client object where we can use the feast service internal or external link when we are working on K8s, which it doesn't exist anymore (or I did not look properly). To resume, I've managed to deploy feast on Kubernetes but my UI is empty since it can't be uploaded on real time.

[tokoko]

@Al4DIN pre-0.9 feast and the current one are so different, they might as well not share the name. bare-bones feast now for example acts more as a python library with which you can connect to a registry, an online or an offline store all without actually deploying a single component. Having said that, there are some components that can be deployed like Feast UI, feature server and most recently-added registry server as well. So it's not really clear to me what you mean by "deploying feast on Kubernetes". Did you deploy any one of these to k8s?

[Al4DIN]

@tokoko thank you for your response. Well I deployed the feast helm chart of the feature-server, basically the feast UI there take the feature-registry mentioned on the deployment part. My goal was to interact and use this deployed feature registry, (before we used to point on this service internally or externally) so we can upload content.

[tokoko]

@Al4DIN Which version of the chart are you deploying? Seems like the latest version of the charts on master don't contain registry or UI deployments, they are exclusively for feature servers.

[Al4DIN]

@tokoko I'm using the v0.31.0, the problem with these last versions of feast. I used a feature_store.yaml pointing on my online & offline stores but when I do update them I don't get updates on my feast ui since I don't have any methods to use them (we can use the repo_config method on same file but it will be redundant and it doesn't update ui values.