- Workaround calcio not declaring DirectoryOrCreate on hostPath volumes #113 (@consideRatio)
- Reduce system pod startup timeout from 10m to 5m #115 (@consideRatio)
- Update calico from 3.27.0 to 3.27.3 #114 (@consideRatio)
See full changelog for dependabot and pre-commit.ci updates.
Version 4.0.0 drops support for installing k3s version 1.20 - 1.23, to keep testing against those versions don't yet upgrade to v4 of this action.
- Drop support for setting up k3s 1.20 to 1.23, now only 1.24+ #105 (@consideRatio, @manics)
- Rely on k3s to provide cri-dockerd #107 (@consideRatio, @manics)
- Update calico from 3.24.5 to 3.27.0 and cri-dockerd from 0.3.0 to 0.3.9 #106 (@consideRatio, @manics)
- Drop support for setting up k3s 1.20 to 1.23, now only 1.24+ #105 (@consideRatio, @manics)
- dependabot: monthly updates of github actions #92 (@consideRatio)
- Add BSD-3 License #96 (@consideRatio, @minrk)
- docs: make helm 3.5 be documented as required #104 (@consideRatio, @manics)
- Add changelog for 3.1.0 #88 (@consideRatio)
- ci: test with ubuntu:22.04 and relax pin of release action to v2 #103 (@consideRatio, @manics)
See full changelog for dependabot and pre-commit.ci updates.
The following people contributed discussions, new ideas, code and documentation contributions, and review. See our definition of contributors.
(GitHub contributors page for this release)
@consideRatio (activity) | @manics (activity) | @minrk (activity)
- Update cri-dockerd from 0.2.6 to 0.3.0 (only for k3s 1.24+) - now k3s 1.26 is supported #86 (@consideRatio)
- build(deps): bump Actions-R-Us/actions-tagger from 2.0.2 to 2.0.3 #83 (@dependabot)
- Update calico from 3.24.0 to 3.24.5 #81 (@consideRatio)
- Update cri-dockerd from 0.2.5 to 0.2.6 #80 (@consideRatio)
- Fix deprecation of set-output #79 (@consideRatio)
- fix: fail after 10 minutes (previously 5) as image pulling can take time #71 (@consideRatio)
- Fix workaround added in 3.0.1 and adjusted in 3.0.2 #69 (@consideRatio)
- Apply workaround added in 3.0.1 only when possible #67 (@consideRatio)
- Workaround kubectl exec and kubectl logs issues with k3s #64 (@consideRatio)
- Update cri-dockerd from 0.2.3 to 0.2.5 #66 (@consideRatio)
- Update cri-dockerd from 0.2.2 to 0.2.3 #61 (@consideRatio)
- docs: fix readme example to use v3 #60 (@consideRatio)
- The action drops support for use with k8s 1.19 and lower.
- Calico bumped from 3.20 to 3.21 for when k3s 1.20 is used.
- Calico bumped from 3.20 to 3.23 for when k3s 1.21+ is used.
- The
docker-enabled
input now provides cri-dockerd and configures k3s for use against it, and like this we retain support for it with k3s version 1.24+.
- Make cri-dockerd function with calico #54 (@consideRatio)
- Install and use cri-dockerd as a dockershim for k8s 1.24+ support #51 (@consideRatio)
- ci: keep v1/v2/v3... tags updated instead of branches #45 (@consideRatio)
- Drop support for k3s 1.19 or lower, bump calico to 3.21 for k3s 1.20, and calico 3.23 for k3s 1.21+ #43 (@consideRatio)
- Fix some incorrect versions which were modified in v2 #38 (@manics)
- Add changelog for 2.0.0 #36 (@consideRatio)
- ci: test network policies in more situations #52 (@consideRatio)
- ci: test against k3s-channel=latest and use k8s-namespace-report #50 (@consideRatio)
- ci: use pre-commit.ci and dependabot #46 (@consideRatio)
(GitHub contributors page for this release)
With this version we drop support for k8s version 1.16 by bumping the installed
calico resources to version 3.20 that require k8s 1.17+. We also fix a critical
bug for anyone using this action and not explicitly disabling traefik to be
installed as an ingress controller via traefik-enabled: false
.
- Group emitted logs for readability #31 (@consideRatio)
- Fix failing traefik install #34 (@consideRatio)
- fix: restrict kubeconfig permissions to current user to avoid helm's warnings #26 (@consideRatio)
- Bump calico 3.17 to 3.20 - drop support for k8s 1.16 #29 (@consideRatio)
- Update README example #35 (@consideRatio)
- ci: ensure actions-tagger has the permissions to update branches/tags #28 (@consideRatio)
- ci: emit a namespace report of kube-system on failure #27 (@consideRatio)