You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are two edge-cases where arkade chart upgrade picks the wrong tag for an image
Expected Behaviour
Running an update where the latest two tags are: prom/prometheus:v2.44.0 and prom/prometheus:v2.45.0-rc0 should not move from a stable version to an RC
The latest two tags are: moby/buildkit:v0.11.6-rootless and moby/buildkit:v0.11.6. In my YAML file I have: moby/buildkit:v0.11.6-rootless, but the upgrade command just finds the latest and replaces it with: moby/buildkit:v0.11.6 which is wrong
Possible Solution
Detect and extract a semver version
Detect any suffix
When finding the latest tags, make sure the suffix is matched - for the case where it is "" and when it's anything else like "rootless"
Steps to Reproduce (for bugs)
Run helm chart upgrade on a values.yaml like this:
Any PR should have tests that show the original problem is fixed, this may require a little refactoring.
The text was updated successfully, but these errors were encountered:
alexellis
changed the title
Edge-cases where arkade chart upgrade does the wrong thing
Edge-cases where arkade chart upgrade picks the wrong tag
Jun 16, 2023
There are two edge-cases where arkade chart upgrade picks the wrong tag for an image
Expected Behaviour
prom/prometheus:v2.44.0
andprom/prometheus:v2.45.0-rc0
should not move from a stable version to an RCmoby/buildkit:v0.11.6-rootless
andmoby/buildkit:v0.11.6
. In my YAML file I have:moby/buildkit:v0.11.6-rootless
, but the upgrade command just finds the latest and replaces it with:moby/buildkit:v0.11.6
which is wrongPossible Solution
Steps to Reproduce (for bugs)
Wrong output:
Right output:
Context
This makes means additional checking and having to undo/manually change the upgrade steps
See also: https://github.com/alexellis/arkade/blob/master/cmd/chart/upgrade.go
Any PR should have tests that show the original problem is fixed, this may require a little refactoring.
The text was updated successfully, but these errors were encountered: