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: Move release images to quay.io #5047

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

tchughesiv
Copy link
Contributor

@tchughesiv tchughesiv commented Feb 12, 2025

What this PR does / why we need it:

Moving release image to quay.io. With this PR, I've tried to change all necessary CI and image references.

In order for the image pushes to succeed, we'll need the following secrets added to this GH repo's settings.

  • QUAYIO_USERNAME
  • QUAYIO_TOKEN

At the same time, we'll want to delete the following existing secrets -

  • DOCKERHUB_USERNAME
  • DOCKERHUB_TOKEN

Which issue(s) this PR fixes:

Fixes #5046

@tchughesiv tchughesiv force-pushed the quayImages branch 3 times, most recently from ce542e5 to 7d057b9 Compare February 12, 2025 20:26
@tchughesiv
Copy link
Contributor Author

tchughesiv commented Feb 12, 2025

@franciscojavierarceo we might want to wait until right before the next release to merge this... as it will break the existing master deployments/etc that are using docker.io

@tchughesiv tchughesiv marked this pull request as ready for review February 12, 2025 21:12
@tchughesiv tchughesiv requested a review from a team as a code owner February 12, 2025 21:12
@redhatHameed
Copy link
Contributor

Any change required for root Makefile-> https://github.com/feast-dev/feast/blob/master/Makefile#L531

@tchughesiv
Copy link
Contributor Author

@redhatHameed no, everything is defined via CI w/ the REGISTRY env var. The line you linked to is a dev image build with no registry assigned. Same as it is today.

@redhatHameed
Copy link
Contributor

@redhatHameed no, everything is defined via CI w/ the REGISTRY env var. The line you linked to is a dev image build with no registry assigned. Same as it is today.

Thanks, make sense.

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.

Migrate Feast Release Images from Docker to Quay
2 participants