You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* update min_ansible_version to 2.15
* use own githubixx Vagrant boxes
* replace injected ansible_* facts usage with ansible_facts[...] (prepares for ansible-core 2.24 where INJECT_FACTS_AS_VARS default changes)
* Molecule verify: check worker services healthy
* Verify on each worker: kubelet and kube-proxy services are enabled/running, and their config files exist with expected permissions / node joined and Ready
* Molecule verify: from control host, assert each worker appears in kubectl get nodes and is Ready
* Molecule verify: check if role configuration is applied
* Molecule: Assert expected kubelet/kube-proxy settings from this role are present (e.g., kubelet config path, kube-proxy mode/config path), not just service status.
* Molecule: check binary/version consistency
* Molecule verify: check if certificates/kubeconfigs are present
* Molecule verify: validate worker certs + kubeconfig files exist and are readable by root only as expected
* Molecule verify: add smoke test
* update README/CHANGELOG
* fix typo in README
Copy file name to clipboardExpand all lines: README.md
+21-9Lines changed: 21 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ This Ansible role is used in [Kubernetes the not so hard way with Ansible - Work
4
4
5
5
## Versions
6
6
7
-
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 `30.0.0+1.33.6` means this is release `30.0.0` of this role and it's meant to be used with Kubernetes version `1.33.6` (but should work with any K8s 1.33.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.
7
+
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 `31.0.0+1.34.4` means this is release `31.0.0` of this role and it's meant to be used with Kubernetes version `1.34.4` (but should work with any K8s 1.34.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.
8
8
9
9
## Requirements
10
10
@@ -27,6 +27,18 @@ See full [CHANGELOG.md](https://github.com/githubixx/ansible-role-kubernetes-wor
27
27
28
28
**Recent changes:**
29
29
30
+
## 31.0.0+1.34.4
31
+
32
+
-**UPDATE**
33
+
- update `k8s_ctl_release` to `1.34.4`
34
+
35
+
-**OTHER**
36
+
- replace injected `ansible_*` facts usage with `ansible_facts[...]` (prepares for ansible-core 2.24 where `INJECT_FACTS_AS_VARS` default changes)
37
+
38
+
-**MOLECULE**
39
+
- use own [githubixx Vagrant boxes](https://portal.cloud.hashicorp.com/vagrant/discover/githubixx)
40
+
- add more checks in `verify.yml`
41
+
30
42
## 30.0.0+1.33.6
31
43
32
44
-**UPDATE**
@@ -99,7 +111,7 @@ See full [CHANGELOG.md](https://github.com/githubixx/ansible-role-kubernetes-wor
0 commit comments