28.0.0+1.31.5 (#56)

* fix typo

* update .gitignore

* update k8s_worker_release to 1.31.5

Author: githubixx

.gitignore

@@ -1,3 +1,4 @@
 *.swp
 *.retry
+.ansible
 .vscode

CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 28.0.0+1.31.5
+
+- **UPDATE**
+  - update `k8s_worker_release` to `1.31.5`
+
 ## 27.0.1+1.30.9
 
 - **UPDATE**
@@ -87,7 +92,7 @@
 
 - **FEATURE**
   - When downloading the Kubernetes binaries the task checks the SHA512 checksum.
-  - Introduce `k8s_worker_api_endpoint_host` and `k8s_worker_api_endpoint_port` variables. Previously `kubelet` and `kube-proxy` where configured to connect to the first host in the Ansible `k8s_controller` group and communicate with the `kube-apiserver` that was running there. This was hard-coded and couldn't be changed. If that host was down the K8s worker nodes didn't receive any updates. Now one can install and use a load balancer like `haproxy` e.g. that distributes requests between all `kube-apiserver`'s and takes a `kube-apiserver` out of rotation if that one is down (also see my Ansible [haproxy role](https://github.com/githubixx/ansible-role-haproxy) for that use case). The default is still to use the first host/kube-apiserver in the Ansible `k8s_controller` group. So behaviorwise nothing changed basically.
+  - Introduce `k8s_worker_api_endpoint_host` and `k8s_worker_api_endpoint_port` variables. Previously `kubelet` and `kube-proxy` where configured to connect to the first host in the Ansible `k8s_controller` group and communicate with the `kube-apiserver` that was running there. This was hard-coded and couldn't be changed. If that host was down the K8s worker nodes didn't receive any updates. Now one can install and use a load balancer like `haproxy` e.g. that distributes requests between all `kube-apiserver`'s and takes a `kube-apiserver` out of rotation if that one is down (also see my Ansible [haproxy role](https://github.com/githubixx/ansible-role-haproxy) for that use case). The default is still to use the first host/kube-apiserver in the Ansible `k8s_controller` group. So behavior-wise nothing changed basically.
   - Add task to generate `kubeconfig` for `kubelet` service (previously this was a separate [playbook](https://github.com/githubixx/ansible-kubernetes-playbooks/tree/v15.0.0_r1.27.5/kubeauthconfig)).
   - Add task to generate `kubeconfig` for `kube-proxy` service (previously this was a separate [playbook](https://github.com/githubixx/ansible-kubernetes-playbooks/tree/v15.0.0_r1.27.5/kubeauthconfig)).
 
@@ -139,7 +144,7 @@
 ## 21.1.0+1.25.9
 
 - update `k8s_release` to `1.25.9`
-- move kubelet parameter `--register-node` to `kubelet.conf` (using the option as parameter is deprected)
+- move kubelet parameter `--register-node` to `kubelet.conf` (using the option as parameter is deprecated)
 - `tasks/main.yml`: add `changed_when: false` to `Disable swap` task
 - `tasks/main.yml`: use `ansible.posix.mount` instead of `ansible.builtin.mount`
 - `kubelet`: remove `--container-runtime` (Flag `--container-runtime` has been deprecated, will be removed in 1.27 as the only valid value is `remote`)
@@ -259,7 +264,7 @@ update `k8s_release` to `1.24.4`
 
 - update `k8s_release` to `1.14.2`
 - update `k8s_cni_plugin_version` to `0.7.5`
-- introduce `k8s_cni_plugin_checksum` variable to determine if CNI plugin tarball has changed and needs to be unarchived
+- introduce `k8s_cni_plugin_checksum` variable to determine if CNI plugin tarball has changed and needs to be unarchive
 
 ## 8.0.1+1.13.5
 
@@ -308,7 +313,7 @@ update `k8s_release` to `1.24.4`
 
 - update `k8s_release` to `1.10.4`
 - introduce `k8s_worker_kubelet_conf_yaml` variable
-- removed deprecated setttings in `k8s_worker_kubelet_settings`
+- removed deprecated settings in `k8s_worker_kubelet_settings`
 - moved settings in `k8s_worker_kubelet_settings` to `k8s_worker_kubelet_conf_yaml`:
   see [kubelet-config-file](https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/)
   see [types.go](https://github.com/kubernetes/kubernetes/blob/release-1.10/pkg/kubelet/apis/kubeletconfig/v1beta1/types.go)
@@ -328,7 +333,7 @@ update `k8s_release` to `1.24.4`
 
 ## r4.1.0_v1.9.3
 
-- remove obsolet kubeconfig.j2 template
+- remove obsolete kubeconfig.j2 template
 
 ## r4.0.0_v1.9.3
 

README.md

@@ -4,7 +4,7 @@ This Ansible role is used in [Kubernetes the not so hard way with Ansible - Work
 
 ## Versions
 
-I tag every release and try to stay with [semantic versioning](http://semver.org). If you want to use the role I recommend to checkout the latest tag. The master branch is basically development while the tags mark stable releases. But in general I try to keep master in good shape too. A tag `27.0.1+1.30.9` means this is release `27.0.1` of this role and it's meant to be used with Kubernetes version `1.30.9` (but should work with any K8s 1.30.x release of course). If the role itself changes `X.Y.Z` before `+` will increase. If the Kubernetes version changes `X.Y.Z` after `+` will increase too. This allows to tag bugfixes and new major versions of the role while it's still developed for a specific Kubernetes release. That's especially useful for Kubernetes major releases with breaking changes.
+I tag every release and try to stay with [semantic versioning](http://semver.org). If you want to use the role I recommend to checkout the latest tag. The master branch is basically development while the tags mark stable releases. But in general I try to keep master in good shape too. A tag `28.0.0+1.31.5` means this is release `28.0.0` of this role and it's meant to be used with Kubernetes version `1.31.5` (but should work with any K8s 1.31.x release of course). If the role itself changes `X.Y.Z` before `+` will increase. If the Kubernetes version changes `X.Y.Z` after `+` will increase too. This allows to tag bugfixes and new major versions of the role while it's still developed for a specific Kubernetes release. That's especially useful for Kubernetes major releases with breaking changes.
 
 ## Requirements
 
@@ -14,7 +14,7 @@ You also need [containerd](https://github.com/githubixx/ansible-role-containerd)
 
 ## Supported OS
 
-- Ubuntu 20.04 (Focal Fossa) (reaches EOL April 2024 - not recommended)
+- Ubuntu 20.04 (Focal Fossa) (reaches EOL April 2025 - not recommended)
 - Ubuntu 22.04 (Jammy Jellyfish)
 - Ubuntu 24.04 (Noble Numbat) (recommended)
 
@@ -28,6 +28,11 @@ See full [CHANGELOG.md](https://github.com/githubixx/ansible-role-kubernetes-wor
 
 **Recent changes:**
 
+## 28.0.0+1.31.5
+
+- **UPDATE**
+  - update `k8s_worker_release` to `1.31.5`
+
 ## 27.0.1+1.30.9
 
 - **UPDATE**
@@ -63,7 +68,7 @@ See full [CHANGELOG.md](https://github.com/githubixx/ansible-role-kubernetes-wor
 roles:
   - name: githubixx.kubernetes_worker
     src: https://github.com/githubixx/ansible-role-kubernetes-worker.git
-    version: 27.0.1+1.30.9
+    version: 28.0.0+1.31.5
 ```
 
 ## Role Variables
@@ -91,7 +96,7 @@ k8s_worker_pki_dir: "{{ k8s_worker_conf_dir }}/pki"
 k8s_worker_bin_dir: "/usr/local/bin"
 
 # K8s release
-k8s_worker_release: "1.30.9"
+k8s_worker_release: "1.31.5"
 
 # The interface on which the Kubernetes services should listen on. As all cluster
 # communication should use a VPN interface the interface name is

defaults/main.yml

@@ -21,7 +21,7 @@ k8s_worker_pki_dir: "{{ k8s_worker_conf_dir }}/pki"
 k8s_worker_bin_dir: "/usr/local/bin"
 
 # K8s release
-k8s_worker_release: "1.30.9"
+k8s_worker_release: "1.31.5"
 
 # The interface on which the Kubernetes services should listen on. As all cluster
 # communication should use a VPN interface the interface name is