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
At the moment I believe when a new version of flagger-k6-webhook is released it just gets tagged with 'latest'.
Would it be possible to also tag the new images with the actual version as well please? For example, k6-loadtester-1.2.0 was released back in October but there are no images available with this tag from what I can te;ll.
At Aviva, we prefer to use a tagged 'version' of each 3rd party image so that any upgrades of the image on our clusters is a deliberate action rather than being caught out by accidentally downloading a newer version without realising it.
The text was updated successfully, but these errors were encountered:
Not really. This might have been from a time when the helm chart was experimental while the code itself had already proven itself. @julienduchesne do you perhaps still remember the reasoning there? If possible, we should probably sync them up (so give the helm chart also a 1.x) 🙂
At the moment I believe when a new version of flagger-k6-webhook is released it just gets tagged with 'latest'.
Would it be possible to also tag the new images with the actual version as well please? For example, k6-loadtester-1.2.0 was released back in October but there are no images available with this tag from what I can te;ll.
At Aviva, we prefer to use a tagged 'version' of each 3rd party image so that any upgrades of the image on our clusters is a deliberate action rather than being caught out by accidentally downloading a newer version without realising it.
The text was updated successfully, but these errors were encountered: