Releases: sapcc/maintenance-controller
Releases · sapcc/maintenance-controller
v0.11
v0.10
v0.9
Breaking change 💥:
- The maintenance-controller is now less strict about profiles in
cloud.sap/maintenance-profile
, which are not present in the configuration. These are now silently ignored (previously such nodes where skipped entierly).
Other changes 🎉:
- Certain dates can now be excluded from the timewindow check plugin
v0.8
v0.7
There should be no breaking change. 🎉
- The affinity plugin now only considers nodes, which are
in-maintenance
caused by the same profile. This resolves some unnecessary blocking. - Fixed a nil pointer deref in the affinity plugin.
- Added kubernikus integration, which checks for kubelet/API server version mismatches and can delete nodes from OpenStack.
- Added nodecount plugin, which checks that at least a specified amount of nodes is present in a cluster.
v0.6
There should be no breaking change. 🎉
- The stagger check plugin now supports a
parallel
config option, which enables nodes to "race" for multiple leases. The configured lease name is appended with-INDEX
- The leases used by the stagger check plugin are now only grabbed by nodes, if they actual do a state transition. This resolves some unnecessary blocking that could occur.
- Added the affinity check plugin, which helps with scheduling pods on operational nodes to minimize downtime.
v0.5
Breaking change 💥:
- The
slackThread
notification plugin now requires atitle
to be configured, which is displayed directly in the slack channel. The messages generated by each node appear as replies.
Other changes 🎉:
- Renamed the leader election lease, the old one can be deleted
- The ESX controller now reloads parts of its configuration on each reconciliation, so pod restarts may be avoided
- Updated to go 1.17