feat(talos): Allow users to include talhelper patches

[wasurerarenai]

Talhelper allows us to include external patch files outside of the main talconfig.yaml. We can use this feature to allow the user to create patches that can be maintained separately from the template generated talconfig. This can be used similarly to this PR for talos specific overrides.

When enabling distribution.talos.user_patches the includes for the following files are added to the generated talconfig.yaml. These patches are applied to the talconfig file's sections of the same name.

• kubernetes/talos/patches/controlPlane.yaml
• kubernetes/talos/patches/global.yaml
• kubernetes/talos/patches/node_name.yaml (name from nodes.inventory.[].name)
• kubernetes/talos/patches/worker.yaml

I haven't figured out how to get makejinja (or similar like ansible/go-task) to optionally generate these as empty files if they don't already exist. The goal is to not stomp these files each time we update our local repo with the latest changes from the template repo. These are particularly useful for nodes that have specific differences from the global defaults due to different worker hardware, existance as a virtual machine, or similar.

[onedr0p]

Looks like the CI is not happy with the worker patches.

[wasurerarenai]

Added the missing logic check. This is one way we can do this with regards to @wouterbouvy's earlier patch. This only generates the "worker.patches" node if the user_patches option is now enabled.

The other option would be separating the logic checks which when user_patches is not enabled would generate an "empty" worker.patches block which doesn't affect talhelper's genconfig run, but looks messier. This however isolates the user_patches check.

Other option looks like:

{% if nodes.inventory | selectattr('controller', 'equalto', False) | list | length %}
worker:
  patches:
    {% if distribution.talos.user_patches %}
    # User specified worker patches
    - "@./patches/worker.yaml"
    {% endif %}
{% endif %}

Either way, I'd prefer it if other code in the template knew how to generate the empty patch files like running mkdir kubernetes/talos/patches && touch kubernetes/talos/patches/{controlPlane,global,worker,node_name}.yaml does. We could separate out the different patch blocks with more config.yaml, but I was afraid of adding too much more cruft...

distribution:
  type: talos
  talos:
    user_patches:
      global: true
      controlPanel: true
      worker: true
      node: true

[onedr0p]

I think you current change here is good, thanks!