Add new versions.json and update build and release workflow to use it #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kevjt
reviewed
Sep 30, 2024
kevjt
reviewed
Oct 1, 2024
kevjt
reviewed
Oct 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Due to Kubernetes image caching, we realised that customers were unlikely to be receiving the latest version of the worker tools.
This is a problem as we have now added
curlto the image (#1), for use as part of automatic upgrades, but due to the cached image, it may not be on the image when the agent goes to perform the upgrade.This is because we previous overwrote the image with the same tag, but just different contents.
This PR changes this to have a random 6 char hash suffix on all
maintags, so the tag1.30now is1.30-X5msD0. This means that we can version/revise the container image and have a different tag.We are also now publishing a tag with all the versions of the tools in the tag, e.g.
kube1.31.4-helm3.16.1-pwsh7.4.5-X5msD0This PR also changes the build and deployment process to be based on a
versions.jsonfile in the root of this repo, which now contains the versions of Kubectl we are build for, the Helm & Powershell versions, as well as the version considered "latest" (e.g. gets thelatesttag) and also what revision we are up to.This means that releasing a new version is now a PR activity, rather than an adhoc workflow run