feat(all): Add release version to binaries #6912
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
When customers have issues dpeloying new releases, from looking at their logs, it's hard to tell if we're looking at the previous version or newly deployed version. This PR injects the release tag at compile time for binaries:
It will print the version to the logs when the pod spins up. Additionally added
-versionas an arg, which will print the version and exit.Summary of changes
scheduler/v2.10.0operator/v2.10.0which all point to the same commit, it won't make any sense to have the operator to print versionscheduler/v2.10.0for example. Instead we just set the tag provided by the releaser with${{ github.event.inputs.docker-tag }}. We should look at if we really need all these different tags and can simplify it.Checklist
Testing