Upstream
/
ansible-role-k3s
mirror of https://github.com/PyratLabs/ansible-role-k3s.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
ansible-role-k3s/CHANGELOG.md

3.4 KiB
Raw Blame History

Change Log

2020-12-12, v2.2.0

Notable changes

  • Use of FQCNs enforced, minimum Ansible version now v2.10
  • k3s_etcd_datastore no longer experimental after K3s version v1.19.5+k3s1
  • Docker marked as deprecated for K3s > v1.20.0+k3s1

Breaking changes

  • Use of FQCNs enforced, minimum Ansible version now v2.10
  • Use of Docker requires k3s_use_unsupported_config to be true after v1.20.0+k3s1

2020-12-05, v2.1.1

Notable changes

  • Fixed link to documentation.

2020-12-05, v2.1.0

Notable changes

  • Deprecated configuration check built into validation steps.
  • Removed duplicated tasks for single node cluster.
  • Added documentation providing quickstart examples and common operations.
  • Fixed data-dir configuration.
  • Some tweaks to rootless.
  • Fix draining and removing of nodes.

Breaking changes

  • k3s_token_location now points to a file location, not a directory.
  • k3s_systemd_unit_directory renamed to k3s_systemd_unit_dir
  • Removed k3s_node_data_dir as this is now configured with data-dir in k3s_server and/or k3s_agent.

Known issues

  • Rootless is still broken, this is still not supported as a method for running k3s using this role.

2020-11-30, v2.0.2

Notable changes

  • Updated issue template and information collection tasks.

2020-11-30, v2.0.1

Notable changes

  • Fixed a number of typos in the README.md
  • Updated the meta/main.yml to put quotes around minimum Ansible version.

2020-11-29, v2.0.0

Notable changes

  • #64 - Initial release of v2.0.0 of ansible-role-k3s.
  • Minimum supported k3s version now: v1.19.1+k3s1
  • Minimum supported Ansible version now: v2.10.0
  • #62 - Remove all references to the word "master".
  • #53 - Move to file-based configuration.
  • Refactored to avoid duplication in code and make contribution easier.
  • Validation checks moved to using variables defined in vars/

Breaking changes

File based configuration

Issue #53

With the release of v1.19.1+k3s1, this role has moved to file-based configuration of k3s. This requires manuall translation of v1 configuration variables into configuration file format.

Please see: https://rancher.com/docs/k3s/latest/en/installation/install-options/#configuration-file

Minimum supported k3s version

As this role now relies on file-based configuration, the v2.x release of this role will only support v1.19+ of k3s. If you are not in a position to update k3s you will need to continue using the v1.x release of this role, which will be supported until March 2021.

Minimum supported ansible version

This role now only supports Ansible v2.10+, this is because it has moved on to using FQDNs, with the exception of set_fact tasks which have been broken and the fixes have not yet been backported to v2.10.

The use of FQDNs allows for custom modules to be introduced to override task behavior. If this role requires a custom ansible module to be introduced then this can be added as a dependency and targeted specifically by using the correct FQDN.