Repository navigation
Improve the feast-feature-server helm chart's Service template #4160
Description
Expected Behavior
Deploying multiple feature servers in the same namespace with the python helm chart should complete successfully.
Current Behavior
Only the first installation to a namespace completes successfully.
Steps to reproduce
$ helm install example1 feast-charts/feast-feature-server --set feature_store_yaml_base64=$(base64 feature_store.yaml)
NAME: example1
LAST DEPLOYED: Mon Apr 29 13:55:16 2024
NAMESPACE: default
STATUS: deployed
REVISION: 1
TEST SUITE: None
$ helm install example2 feast-charts/feast-feature-server --set feature_store_yaml_base64=$(base64 feature_store.yaml)
Error: INSTALLATION FAILED: rendered manifests contain a resource that already exists. Unable to continue with install: Service "feast-feature-server" in namespace "default" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "example2": current value is "example1"Specifications
- Version: 0.37.1
- Platform: Kubernetes
Possible Solution
Change the feast-feature-server helm chart's service.yaml template to use the feast-feature-server.fullname like the deployment.yaml template does. The service template currently uses feast-feature-server.name.
Activity