7.0.0+1.12.1 (#19)

* update Cilium to v1.12.1

* fix type in README

* add Github release action

* update CHANGELOG

.github/workflows/release.yml

@@ -0,0 +1,39 @@
+---
+# This workflow requires a GALAXY_API_KEY secret present in the GitHub
+# repository or organization.
+#
+# See: https://github.com/marketplace/actions/publish-ansible-role-to-galaxy
+# See: https://github.com/ansible/galaxy/issues/46
+
+name: Release
+on:
+  push:
+    tags:
+      - '*'
+
+defaults:
+  run:
+    working-directory: 'githubixx.cilium_kubernetes'
+
+jobs:
+  release:
+    name: Release
+    runs-on: ubuntu-latest
+    steps:
+      - name: Check out the codebase.
+        uses: actions/checkout@v2
+        with:
+          path: 'githubixx.cilium_kubernetes'
+
+      - name: Set up Python 3.
+        uses: actions/setup-python@v2
+        with:
+          python-version: '3.x'
+
+      - name: Install Ansible.
+        run: pip3 install ansible-core
+
+      - name: Trigger a new import on Galaxy.
+        run: >-
+          ansible-galaxy role import --api-key ${{ secrets.GALAXY_API_KEY }}
+          $(echo ${{ github.repository }} | cut -d/ -f1) $(echo ${{ github.repository }} | cut -d/ -f2)

CHANGELOG.md

@@ -1,6 +1,11 @@
 Changelog
 ---------
 
+**7.0.0+1.12.1**
+
+- upgrade to Cilium v1.12.1
+- add Github release action to push new release to Ansible Galaxy
+
 **6.0.4+1.11.6**
 
 - upgrade to Cilium v1.11.6

README.md

@@ -20,7 +20,7 @@ Role Variables
 
 ```
 # Helm chart version
-cilium_chart_version: "1.11.6"
+cilium_chart_version: "1.12.1"
 
 # Helm chart name
 cilium_chart_name: "cilium"
@@ -131,7 +131,7 @@ And finally if you want to get rid of Cilium you can delete all resources again:
 ansible-playbook --tags=role-cilium-kubernetes --extra-vars action=delete k8s.yml
 ```
 
-If you don't have any CNI plugins configured this will cause `kublet` process on the Kubernetes worker nodes to issue CNI errors every now and then because there is no CNI related stuff anymore and of course connectivity between pods on different hosts will be gone together with any network policies and stuff like that.
+If you don't have any CNI plugins configured this will cause `kubelet` process on the Kubernetes worker nodes to issue CNI errors every now and then because there is no CNI related stuff anymore and of course connectivity between pods on different hosts will be gone together with any network policies and stuff like that.
 
 Example Playbook
 ----------------

defaults/main.yml

@@ -1,6 +1,6 @@
 ---
-# Helm chart version (uses Cilium v1.11.6)
-cilium_chart_version: "1.11.6"
+# Helm chart version (uses Cilium v1.12.1)
+cilium_chart_version: "1.12.1"
 
 # Helm release name
 cilium_release_name: "cilium"