The Configuration Reference will walk through how to configure each Feast component:
Available Configuration Properties for Feast Core, Serving and Job Controller can be referenced from the corresponding
application.yml of each component:
Configuration Properties for Feast Core, Serving and Job Controller are defined depending on Feast is deployed:
Docker Compose deployment - Feast is deployed with Docker Compose.
Kubernetes deployment - Feast is deployed with Kubernetes.
Direct Configuration - Feast is built and run from source code.
Configuration Properties from
application.yml can be set for each Feast component deployed using docker compose at:
The Kubernetes Feast Deployment is configured via the Feast Helm Chart's
# values.yamlfeast-core:enabled: true # whether to deploy the feast-core subchart to deploy Feast Core.# feast-core subchart specific config.gcpServiceAccount:enabled: true# ....
A reference of the sub chart specific configuration can found in its
Configuration Properties can be set via
application-override.yaml for each component in
# values.yamlfeast-core:# ....application-override.yaml:# application.yml config properties for Feast Core.# ...
If Feast is built and running from source, configuration Properties can be set directly in the Feast component's
Configuration options for both the Feast CLI and Feast Python SDK can be defined in the following locations, in order of precedence:
1.Command line arguments or initialized arguments: Passing parameters to the CLI or instantiating the Feast Client object with specific parameters will take precedence above other parameters.
# Set option as command line arguments.feast config set core_url "localhost:6565"
# Pass options as initialized arguments.client = Client(core_url="localhost:6565",project="default")
2. Environmental variables: Environmental variables can be set to provide configuration options. They must be prefixed with
FEAST_ . For example
FEAST_CORE_URL=my_feast:6565 FEAST_PROJECT=default feast projects list
3. Configuration file: Options with the lowest precedence are configured in the Feast configuration file. Feast will look for or create this configuration file in
~/.feast/config if it does not already exist. All options must be defined in the
[general] section of this file.
[general]project = defaultcore_url = localhost:6565
Available configuration options for Python SDK/CLI be found here.
The Feast Java and Go SDK is configured via arguments passed when instantiating the Feast Client:
// configure serving host and port.cli := feast.NewGrpcClient("localhost", 6566)
Available configuration parameters can be found in the Go SDK API reference.
// configure serving host and port.client = FeastClient.create(servingHost, servingPort);
Available configuration parameters can be found in the Java SDK API reference.