When using a user defined node ip on a dual stack cluster,
k3s_node_ip will contain "ipv4,ipv6" IP. In order to properly set
the registration IP, the first (preferred) IP in the list is used,
and if it is the IPv6 IP it will be URL wrapped.
I found a bug where my custom containerd registries config wasn't live,
despite the correct `notify` handlers being specified in the
'Ensure containerd registries file exists' task.
This change fixes that by ensuring the handlers get triggered.
* fix(ansible-lint): FQDN and `name`
* fix(ansible-lint): add `name` and FQDN for module call
* fix(ansible-lint): add `name` to tasks and FQDN for module
* fix(ansible-lint): add task `name` and FQDN for module calls
* fix(ansible-lint): last `include_tasks`
* fix(ansible-lint): add task names and FQDN
* refactor: `Ensure` to `Run`
* [skip ci]refactor: add exist and seperate ensure installed node task, mention build cluster
* [skip ci]refactor: Pipe seperator
* [skip ci]refactor: run
* refactor: remove quotes as other files don't use them
For templated vars in task name
* [skip ci]refactor: task names, use `Run`
* [skip ci]refactor: use variable name in task name
* [skip ci]refactor: task names
* [skip ci]refactor: add service mgr in task name
* [skip ci]refactor: add task names and module FQDNs
* [skip ci]refactor: fix task name
* [skip ci]refactor: add -
* [skip ci]refactor: include task names and FQDNs
* [skip ci]refactor: add task names and FQDNs
* [skip ci]: ignore `name[template]`
* refactor: `when` clause for `block` should be before `block`
* fix: https://github.com/ansible-community/molecule/issues/3883
* refactor: molecule lint command was removed in version `5.0.0`
Use separate CI job step to run linting instead.
* [skip ci]refactor: noqa for command tasks
Subject to change
* refactor: use Ubuntu 22.04
Suspect issues with Molecule tests are related to cgroups v2.
in an air gapped environment the machine will not be able to check sha checksums or information
around the binary so we should ignore the tasks in that scenario
in an air gapped environment the machine will not be able to check sha checksums or information
around the binary so we should ignore the tasks in that scenario
airgap installs allow users to deploy k3s in a situation where the server is not internet connected
and therefore unable to download anything externally
