Expected Behavior
I should be able to run a Feature Store on Kubernetes using the Feast Operator by following the operator-quickstart guide.
Current Behavior
The initialization process fails because the environment lacks git, which prevents the repository from being cloned. This subsequently causes feast-apply to fail because the required configuration files are never created.
Error Logs:
│ feast-apply Can't find feature repo configuration file at /feast-data/credit_scoring_local/feature_repo/feature_store.yaml.
│
│ feast-init Creating feast repository...
│ feast-init git clone https://github.com/feast-dev/feast-credit-score-local-tutorial /feast-data/credit_scoring_local && cd /feast-data/credit_scoring_loc │
│ feast-init bash: line 3: git: command not found
│ feast-init bash: line 4: /feast-data/credit_scoring_local/feature_repo/feature_store.yaml: No such file or directory
│ feast-init Feast repo creation complete
Steps to reproduce
- Clone the
feast repository.
- Navigate to
examples/operator-quickstart.
- Follow the instructions provided in the README to deploy on Kubernetes.
Alternatively, run:
kubectl apply -f https://raw.githubusercontent.com/feast-dev/feast/refs/heads/stable/infra/feast-operator/config/samples/v1_featurestore_git.yaml
Specifications
- Version: 0.62.0
- Platform: Kubernetes
- Subsystem: Feast Operator / Initialization
Possible Solution
The error bash: line 3: git: command not found indicates that the container image used by the Feast Operator (or the specific job running feast-init) does not have git installed.
Suggested Fixes:
- Update the Image: Ensure the base image used for the initialization process includes
git.
- Alternative Initialization: Modify the
feast-init script to use curl or wget to download the repository as a ZIP archive instead of relying on git clone.
Expected Behavior
I should be able to run a Feature Store on Kubernetes using the Feast Operator by following the operator-quickstart guide.
Current Behavior
The initialization process fails because the environment lacks
git, which prevents the repository from being cloned. This subsequently causesfeast-applyto fail because the required configuration files are never created.Error Logs:
Steps to reproduce
feastrepository.examples/operator-quickstart.Alternatively, run:
Specifications
Possible Solution
The error
bash: line 3: git: command not foundindicates that the container image used by the Feast Operator (or the specific job runningfeast-init) does not havegitinstalled.Suggested Fixes:
git.feast-initscript to usecurlorwgetto download the repository as a ZIP archive instead of relying ongit clone.