Currently, the adoption-center image that the operator uses to deploy does not contain a tag. Which means, if you are making local changes to that module, skaffold will build and tag the image, but because the operator deployment manifest doesn't use that new image tag, operator will still set adoption-center image without tag. With the current deployment logic, you will need to either manually update that deployment manifest with the correct image tag to be able to test your adoption-center changes.
Ways to solve this:
- Add pre-deploy hook to modify that deployment manifest yaml with the generated tag (
yq or sed).
- Add kustomize overlay to to overwrite that image tag
- Use a proper templating tool (helm or ytt)
- ...
Since this is only a sample app, it's not crucial to have this issue. But if you are using this in production, you should find a better way to manage your images.
Currently, the adoption-center image that the operator uses to deploy does not contain a tag. Which means, if you are making local changes to that module,
skaffoldwill build and tag the image, but because the operator deployment manifest doesn't use that new image tag, operator will still setadoption-centerimage without tag. With the current deployment logic, you will need to either manually update that deployment manifest with the correct image tag to be able to test your adoption-center changes.Ways to solve this:
yqorsed).Since this is only a sample app, it's not crucial to have this issue. But if you are using this in production, you should find a better way to manage your images.