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

chore: Rename Helm Operator #4569

Merged
merged 1 commit into from
Sep 30, 2024

Conversation

tchughesiv
Copy link
Contributor

What this PR does / why we need it:

This PR is to more clearly define that the existing feast operator is actually a Helm-based operator. This is important as we are likely to introduce a new Go-based operator in the near future.
Prerequisite to #4561

Misc

@franciscojavierarceo Before we merge this PR, we'll require a new docker repo named "feast-helm-operator". It should replicate the permissions of the existing feast-operator repo below. The new Go-based operator would use the existing "feast-operator" repo going forward. We'll make a swap.
https://hub.docker.com/r/feastdev/feast-operator

Copy link
Member

@franciscojavierarceo franciscojavierarceo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@franciscojavierarceo
Copy link
Member

Should we use this as an opportunity to migrate to quay instead?

@tchughesiv
Copy link
Contributor Author

imo, the move to quay.io should start with our pre-release GCR images @ gcr.io/kf-feast. the docker.io images are our "release" images and probably shouldn't be the first to go.

Copy link
Member

@franciscojavierarceo franciscojavierarceo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved

@franciscojavierarceo franciscojavierarceo merged commit ff3d597 into feast-dev:master Sep 30, 2024
26 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants