Config files for Kubernetes are 404

[Valentin Viennot]

At lest on the PostgreSQL and the MySQL images docs, the links to the Kubernetes config files are broken:

https://hub.docker.com/r/ubuntu/mysql
https://git.launchpad.net/~canonical-server/ubuntu-docker-images/+git/mysql/plain/examples/mysql-deployment.yml

As it seems, a `?h=<branch>` parameter is required for the URL to match with a file. Not sure why it wasn't required before? As a consequence, all these files from the READMEs are now returning 404s.

[Athos Ribeiro (athos-ribeiro)]

This is interesting. Now we have a single page pointing to all the tags, and although most (if not all) examples are the same for all branches for now, should we add pointers for different examples here? This would require referencing the branches in the data/${image}.yaml data files

Alternatively, a simple fix, which would require no further changes, would be to either set the latest branch as the default one, or to create a development branch for all the images and set that as the default branch (and always update that before forking it for a new image release). Thoughts?

[Sergio Durigan Junior (sergiodj)]

Thanks for looking into this, Athos.

My preference would be for the first approach: add links to the different supported versions of the files. I think it should be possible to calculate the branch name using the information already in the .yaml file, so there should be no need to add a new field there.

Setting the latest branch as the default one is not optimal because it'd add yet another manual step to our (already non-trivial) list of manual things we need to do every release, IMO.

But that's just my two cents, of course. I'd like to hear Valentin's opinions on this one, since he's been driving this effort.

Thanks.

[Valentin Viennot (valentinviennot)]

Oops, I never replied back here. I think we can now close this!

The procedure is not ideal but what I did is:

- add the h?= parameter to the URLs in the data.yaml
- update URLs when updating the YAML file, when relevant