GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Improve the `feast-feature-server` helm chart's Service template · Issue #4160 · feast-dev/feast

Improve the feast-feature-server helm chart's Service template #4160

New issue
Copy link
New issue
Copy link
Closed
#4161
Closed
Improve the feast-feature-server helm chart's Service template#4160
#4161
Copy link
Labels
kind/bugpriority/p2

Description

@tchughesiv
tchughesiv
opened on Apr 29, 2024
Issue body actions

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

  1. tchughesiv
    added
    kind/bug
    priority/p2
    on Apr 29, 2024
  2. jeremyary
    closed this as completedin #4161on May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugpriority/p2

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions
      You are visitor 01402520 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.