Skip to content

Repo still refers to old Docker image in places #338

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

Closed
coro opened this issue Sep 14, 2020 · 2 comments
Closed

Repo still refers to old Docker image in places #338

coro opened this issue Sep 14, 2020 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@coro
Copy link
Contributor

coro commented Sep 14, 2020

Describe the bug

The repo references the old Docker image rabbitmqoperator/rabbitmq-cluster-kubernetes-operator-dev and rabbitmqoperator/rabbitmq-cluster-kubernetes-operator in places, which were replaced by rabbitmqoperator/cluster-operator-dev and rabbitmqoperator/cluster-operator, respectively.

Expected behavior
I would expect both of these image names to be replaced with the new image name. It would be worth investigating where in our repo & tooling the old image is referenced, then updating to the new image name.

Additional context

Once these deletions are made, we can remove the old images from Dockerhub.

@coro coro added the bug Something isn't working label Sep 14, 2020
@ChunyiLyu
Copy link
Contributor

Remember to update this file as it uses the docker image as a placeholder string when using kustomize edit image: https://github.com/pivotal/rabbitmq-for-kubernetes-ci/blob/master/tasks/operator-system-tests/task.yml

@Zerpet
Copy link
Member

Zerpet commented Sep 21, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants