* 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.
This release also fixes:
- #38 : removing the --disable-agent option. Please use node taints.
- #39 : clarified where jmespath should be installed in README.md
Fixes#16
This is because without a CNI, nodes will never be ready and the task
will fail. You need to deploy your choice of CNI manually (such as
Calico) then check the state of the cluster using `kubectl get nodes`.
1. Now does not remove prerequisite packages, lvm2 was included in
these packages (not good when you use LVM2 for real).
2. Added a bit more idempotency to the shell scripts - only delete if
it exists.
3. Check that the process isn't running and binaries are gone.
