Releases: annismckenzie/k3os-config-operator
v0.3.2: dependency upgrades
This updates the dependencies throughout the project (Go module versions, Docker image versions, GitHub Actions versions).
v0.3.1: crashloop fix
v0.3.1 (2021-01-24)
Fixed bugs:
- Stray --enable-leader-election flag causes operator to crashloop #42 (annismckenzie)
v0.3.0: e2e test suite 🎉
Implemented enhancements:
- Add e2e test suite #27
Merged pull requests:
- Add missing config file sync feature to the README #39 (annismckenzie)
- Add Go Report Card badge #37 (annismckenzie)
- Stop skipping tests on the main branch #36 (annismckenzie)
- Add coverage status badge to README #35 (annismckenzie)
- Upgrade k8s.io dependencies: controller-runtime & client libraries #34 (annismckenzie)
- Add e2e test suite #29 (annismckenzie)
- Add roadmap #26 (annismckenzie)
v0.2.0: node config file management 🎉
This release's headline feature is the node config file management. When the secret containing the node config files is updated, the node config file on disk is updated as well (#13). 🎉
Other improvements:
v0.1.2: bugfix for node label reconciliation
This contains a fix for #14.
v0.1.1: hotfix for the initial release
I found a rather critical bug (described in #10). That's now fixed.
v0.1.0: initial version 🎉
This is the initial version of the k3OS Config Operator (what a mouthful).
It includes syncing of labels as well as taints using a set of config.yaml files. These two fields are specifically marked as After the node is first registered in Kubernetes the value of this setting will be ignored.
. Well, no more. Updates to these fields will be applied. The operator only ever touches labels and taints it itself created – so it'll leave all of the existing node labels untouched. You may, of course, change them using the operator at which point they will be managed. Taints can be removed from the list or kept and suffixed with a -
to remove an existing taint but keep it in the config file (dropping the -
suffix will add the taint again).