container release tag concept

[universam1]

Expected Behavior

We are happy to use this great tool! However we are also somwhere uncertain about the release concept of this project which is not working well with tools such as renovateBot.

It would be helpful when all the releases are published as github releases, and the latest container is also backed up with a semver versioned tag.

Actual Behavior

The examples suggest using latest container tag where there is no equivalent semver tag available.

1. it does not match with github releases
2. latest has the other tag v0.1.17-3-g2ccd690 which is not parsed by renovatebot

Steps to Reproduce the Problem

Looking up the registry:

wget -q https://registry.opensource.zalan.do/v1/repositories/teapot/kube-metrics-adapter/tags -O - | jq --sort-keys .

shows v0.1.17-3-g2ccd690 being equivalent to latest

[universam1]

is this related to #258 ?

[mikkeloscar]

@universam1 Currently it works like this: latest always maps to master, whether there is a release or not. We document latest not because we recommend that you should use that, but rather to avoid having old versions documented because we forget to update the example deployments. We recommend that you only use the releases unless you want to test something potentially new only in master.