Create structure for FAQ/Tips&tricks

[housa]

Common pitfalls / FAQ / Tips&Tricks

part of creating this guide encompasses actually setting everything up and running it, any quirks or common pitfalls should be documented in some way, to make it easy for other developers creating a similar setup to find answers to questions not easily googlable.

This should either be it's own section, or maybe embedded in the ADR for the tool?

The main idea is that we link to guides used, and add info on the not so easily readable stuff.

It should be as general as possible, so that it won't need updating every time stuff evolves, but also so it doesn't require all choices to match the guide. i.e. for Talos you need to prebake kernel params into the iso, these are defined by storage solutions, virtualisation, etc. rather than: prebake kernel argument a and b into Talos to make it work for longhorn.