René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Improve the `feast-feature-server` helm chart's Service template","articleBody":"## Expected Behavior \r\nDeploying multiple feature servers in the same namespace with the python helm chart should complete successfully.\r\n\r\n## Current Behavior\r\nOnly the first installation to a namespace completes successfully. \r\n\r\n## Steps to reproduce\r\n```bash\r\n$ helm install example1 feast-charts/feast-feature-server --set feature_store_yaml_base64=$(base64 feature_store.yaml)\r\nNAME: example1\r\nLAST DEPLOYED: Mon Apr 29 13:55:16 2024\r\nNAMESPACE: default\r\nSTATUS: deployed\r\nREVISION: 1\r\nTEST SUITE: None\r\n\r\n$ helm install example2 feast-charts/feast-feature-server --set feature_store_yaml_base64=$(base64 feature_store.yaml)\r\nError: 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\"\r\n```\r\n\r\n### Specifications\r\n\r\n- Version: 0.37.1\r\n- Platform: Kubernetes\r\n\r\n## Possible Solution\r\nChange 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`.","author":{"url":"https://github.com/tchughesiv","@type":"Person","name":"tchughesiv"},"datePublished":"2024-04-29T19:00:41.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/4160/feast/issues/4160"}