Add artifacts naming doc

[mauromorales]

⚠️ let's merge this until all the changes to the artifacts are done, so we don't have to open fixes in case something changes

Relates to kairos-io/kairos#1109

[netlify]

✅ Deploy Preview for kairos-io ready!

Name	Link
🔨 Latest commit	ecd72d0
🔍 Latest deploy log	https://app.netlify.com/sites/kairos-io/deploys/64c77ef0aaecd5000703923d
😎 Deploy Preview	https://deploy-preview-55--kairos-io.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[jimmykarily]

We can merge this PR after the implementation is done: kairos-io/kairos#1109

[mauromorales]

@jimmykarily according to the discussion today we will use tags for the support of the image. Do you know how that looks in the end? Maybe something like:

quay.io/kairos/core-ubuntu-generic:community-v1.0.0

and if that is the case, should we also move the model into the tag?

quay.io/kairos/core-ubuntu-generic:community-generic-v1.0.0

[jimmykarily]

Not "tags", "labels". Like these: https://docs.docker.com/engine/reference/builder/#label

[mauromorales]

Oh cool, I didn't know about this one ... and you can filter them to download? And if so, the question would still apply, should we only have a quay.io/kairos/core-ubuntu:v1.0.0 and you somehow pass labels to filter even further

[jimmykarily]

It seems that you can filter them locally: https://docs.docker.com/engine/reference/commandline/images/#filter
And the web UI of the registry might let you see the labels. But I don't think anyone will be downloading in batches so they would first identify the image they want and then download it, so no need for filtering (?).

An image will be, either community or "official" not both. So they just need to check the label for the image they are interested in.

[mauromorales]

This is just waiting for the 2.4.0 release with the new artifacts names

[Itxaka]

This is done now!