0.13.0+1.7.20

• update containerd to v1.7.20

0.13.0+1.7.19

• FEATURE

  • add support for Ubuntu 24.04

• UPDATE

  • update containerd to v1.7.19

0.12.7+1.7.16

• UPDATE
  • update containerd to v1.7.16

0.12.6+1.7.15

• UPDATE

  • update containerd to v1.7.15

• MOLECULE

  • use alvistack instead of generic Vagrant boxes

0.12.5+1.7.13

What's Changed

• update containerd to v1.7.13 by @githubixx in #28

Full Changelog: 0.12.4+1.7.12...0.12.5+1.7.13

0.12.4+1.7.12

What's Changed

0.12.4+1.7.12

• add task that creates directory specified in containerd_tmp_directory
• fix typo in defaults/main.yml
• Molecule: Change IP addresses
• Molecule: add two new host variables in molecule/default/molecule.yml
• update containerd to v1.7.12
• adjust Github action because of Ansible Galaxy changes

• 0.12.3+1.7.12 by @githubixx in #26
• 0.12.4+1.7.12 by @githubixx in #27

Full Changelog: 0.12.2+1.7.10...0.12.4+1.7.12

0.12.2+1.7.10

What's Changed

• update containerd to v1.7.10
• remove CNI leftovers

• 0.12.2+1.7.10 by @githubixx in #25

Full Changelog: 0.12.0+1.7.8...0.12.2+1.7.10

0.12.0+1.7.8

What's Changed

• add missing configuration options to make containerd work with Kubernetes out of the box: [plugins."io.containerd.grpc.v1.cri"] -> sandbox_image = "registry.k8s.io/pause:3.8" and [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc -> runtime_type = "io.containerd.runc.v2"
• add "Type": "notify" to containerd_config

• 0.12.0+1.7.8 by @githubixx in #24

Full Changelog: 0.11.0+1.7.8...0.12.0+1.7.8

0.11.0+1.7.8

What's Changed

Note This release contains quite a few breaking changes. This mostly happened because cri-containerd-*.tar.gz release bundles are deprecated. Also see cri-containerd.DEPRECATED.txt. So containerd doesn't contain CNI plugins and runc anymore. You can still use this bundle if you use version 0.10.0+1.7.3 of this Ansible role. But for this version I deciced to remove the support already before containerd v2.0 will be released. That means for containerd_flavor only the value base can be used and k8s has been gone. So that means you have to install CNI - Container Network Interface and runc separately. This should happen before you install containerd. You can use my Ansible roles

• For CNI: ansible-role-cni
• For runc: ansible-role-runc

Other changes:

• Breaking containerd_config variable contained a complete dump of all possible containerd configuration settings. The dump was created with containerd config default. So if you just need to execute this command to get all possible configuration options. Since most settings are not relevant I changed the value accordingly and only keep what's different to the default settings. The current settings are intended to be used with a Kubernetes cluster. But in general they should also be a good starting point for standalone installations of containerd. If you had your own containerd_config variable defined this change doesn't affect you.
• Breaking containerd_flavor variable only supports base value. k8s was removed. This variable most probably will be go away in a later release. If you already used base value here the change wont affect you.
• Breaking containerd_archive_k8s variable was removed
• Breaking All runc related resources and variables were removed: containerd_runc_binary_directory, containerd_runc_owner, containerd_runc_group, containerd_runc_binary_mode
• Breaking All crictl related resources and variables were removed: containerd_crictl_config_file, containerd_crictl_config_directory, containerd_crictl_config_directory_mode, containerd_crictl_config_directory_owner, containerd_crictl_config_directory_group, containerd_crictl_config_file_owner, containerd_crictl_config_file_group, containerd_crictl_config_file_mode, containerd_crictl_config_file_content
• Breaking All CNI related resources and variables were removed: containerd_cni_binary_directory, containerd_cni_binary_directory_mode, containerd_cni_binary_owner, containerd_cni_binary_group, containerd_cni_binary_mode, containerd_cni_netconfig_file, containerd_cni_netconfig_directory, containerd_cni_netconfig_directory_mode, containerd_cni_netconfig_file_owner, containerd_cni_netconfig_file_group, containerd_cni_netconfig_file_mode, containerd_cni_netconfig_file_content
• Breaking update to containerd configuration version 2 (that means first line in containerd_config variable is now version = 2)
• update containerd to v1.7.8
• Molecule: improve verification step
• Molecule: increase memory for boxes
• Molecule: rename kvm scenario to default

• 0.11.0+1.7.8 by @githubixx in #23

Full Changelog: 0.10.0+1.7.3...0.11.0+1.7.8

0.10.0+1.7.3

What's Changed

• update containerd to 'v1.7.3`
• add support for Ubuntu 22.04
• BREAKING: remove support for Ubuntu 18.04 (reached end of life)
• BREAKING: When containerd or CNI binaries are upgraded containerd.service will be restarted. Up until this version this only happened when containerd configuration was updated.

Full Changelog: 0.9.0+1.7.0...0.10.0+1.7.3