Getting started with Feast
This guide provides the necessary resources to install Feast alongside Kubeflow, describes the usage of Feast with Kubeflow components, and provides examples that users can follow to test their setup.
For an overview of Feast, please read Introduction to Feast.
Installing Feast with Kubeflow
This guide assumes that you have a running Kubeflow cluster already. If you don’t have Kubeflow installed, then head on over to the Kubeflow installation guide.
Feast can be installed into a running Kubeflow deployment. The process of installing Feast into Kubernetes is documented in the Deploying Feast into Kubernetes guide. Please follow this guide to install Feast into the same Kubernetes cluster as Kubeflow.
Accessing Feast from Kubeflow
Once Feast is installed within the same Kubernetes cluster as Kubeflow, users can access its APIs directly without any additional steps.
Feast APIs can roughly be grouped into the following sections:
Feature definition and management: Feast provides both a Python SDK and CLI for interacting with Feast Core. Feast Core allows users to define and register features and entities and their associated metadata and schemas. The Python SDK is typically used from within a Jupyter notebook by end users to administer Feast, but ML teams may opt to version control feature specifications in order to follow a GitOps based approach.
Model training: The Feast Python SDK can be used to trigger the creation of training datasets and generation of statistics through Feast Serving. The most natural place to use this SDK is to create a training dataset as part of a Kubeflow Pipeline prior to model training.
Model serving: Feast provides three different SDKs for online feature serving, a Python SDK, Java SDK, and Go SDK. These clients are used prior to inference with Model Serving systems like KFServing, TFX, or Seldon.
Feast also comes with example notebooks that users can use to get up to speed.
For more details on Feast concepts please see the Feast documentation
Please use GitHub issues for any feedback, issues, or feature requests.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.