-
Notifications
You must be signed in to change notification settings - Fork 449
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
Source code archive from the release of v5.0.16 uses v5.0.15 image #2210
Comments
please pull the image again, this should be already fixed. thanks for reporting. |
@cesnietor Will these images be updated again when v5.0.16 is released? |
no they won't be - there were done for internal purposes, for all practical purposes v5.0.15 is fine v5.0.16 is just a rebuild of v5.0.15 |
When I get source code tagged with v5.0.16, v5.0.15 is used as the image tag in the manifest.
Expected Behavior
Source codes that tagged v5.0.16 are using v5.0.16 images.
Current Behavior
They use v5.0.15 as follows:
Possible Solution
This repository also seems to have
v5.0.16
branch. And this branch seems to be correct.operator/resources/base/deployment.yaml
Line 26 in 2e51bd3
operator/resources/base/console-ui.yaml
Line 292 in 2e51bd3
I can't see the code for the v5.0.16 tag on GitHub because it seems that if there is a tag and a branch with the same name, the branch always takes precedence.
Downloading the contents of this branch instead will probably yield the correct one.
However, this is an inconsistent approach since there is no branch with a version name other than v5.0.16.
Context
The document recommended customizing the manifest on this repository as a template. I obtained the source code from the latest release, and when I tried to work on the customization, I noticed that the tag names did not match the image names.
Regression
At least in 5.0.15 and 5.0.14, the image and Git tags matched.
Your Environment
The text was updated successfully, but these errors were encountered: