Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a Kubernetes Operator for the Feast Feature Server, to the infra directory #4144

Closed
tchughesiv opened this issue Apr 24, 2024 · 0 comments · Fixed by #4145
Closed

Add a Kubernetes Operator for the Feast Feature Server, to the infra directory #4144

tchughesiv opened this issue Apr 24, 2024 · 0 comments · Fixed by #4145
Labels
kind/feature New feature or request

Comments

@tchughesiv
Copy link
Contributor

tchughesiv commented Apr 24, 2024

Is your feature request related to a problem? Please describe.
We should leverage the power of kubernetes controllers to manage the deployment state of the feast-feature-server. This is more operationally sound, as it can “repair” issues with deployments in a cluster. It also simplifies the management of multiple deployments within a cluster and opens the door to integrations with other operator-based projects.

Describe the solution you'd like
Wrap the existing feast-feature-server helm chart into a simple helm-based operator.

Describe alternatives you've considered
I considered creating a go-based operator instead. This would add significant complexity to the development and maintenance of feast. Given that feast and its users already utilize helm, this seemed unnecessary.

Additional context
This new helm-based operator will leverage a few static kustomize manifests to deploy the operator, but it will utilize the helm chart to deploy the feature server(s) themselves. Users will not have to install helm, the operator will handle everything. Those familiar with the existing helm chart will be able to easily port their settings if they so choose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant