🌱 Community and official images

[mudler]

Is your feature request related to a problem? Please describe.

Currently there are a bunch of flavors/images that we don't test automatically.

This means that, we either test them manually, or rely on user-report to spot bugs.

This approach doesn't scale, and we have discussed the possibility to add automated test, however, this is not a solution for ARM platform images (as RPI or Jetson) neither for certain flavors (rockylinux, fedora, that requires specific cpu settings).

Describe the solution you'd like

We should clearly differentiate in our documentation and in our build artifacts (for example, by using a suffix?) images that are tested automatically by our QA pipelines and those which aren't.

We can, identify the images in two big categories:

• Kairos supported builds
• Community supported builds

Describe alternatives you've considered
Try to cover as much as possible with the CI. however, we are trying to find a general solution that works in most cases, and that doesn't scale with ARM specific images.

Action items

• Identify flavors that are automatically tested
• make it clear in the test matrix why we test what where. E.g. Ubuntu only on all PRs, as much as possible on main, but when only testing one, then something different from Ubuntu to try to catch as many issues as possible.
• Reflect in the docs (Image matrix, .... ) which are official and which not
• Change the build artifacts naming to reflect the change. -> Add a label to the images to reflect the change
• /etc/os-release has a field about whether flavor is officially supported or community supported
• Write a blog post about this change

[mauromorales]

Added action item to document the testing matrix flavors reasoning