Skip to content

Releases: criteo/node-disruption-controller

0.2.1: Fix flaky test when reconciler start before previous one still up

24 Nov 08:31

Choose a tag to compare

between test, the reconciler is stopped and started again.
Stop is not instant but we started a new instance right away.
Since it bind a port, the new one crashed because the old
one didn't release it yet. Instead we wait for the manager to
be properly down before starting a new one

0.2.0

03 Nov 09:58

Choose a tag to compare

Prepare bump to 0.2.0

0.1.2

17 Aug 07:28

Choose a tag to compare

Prepare bump to 0.1.2

0.1.1: Run golangci-lint on pull requests

09 Aug 09:45

Choose a tag to compare

- added golang-ci to make test
- cleaned the test job

Prepare bump to 0.1.0

07 Aug 07:29

Choose a tag to compare

Breaking changes:
- spec.state moved to status.state
- status.impacted* changed to status.impactedBudgets

0.0.6

24 Jul 07:46

Choose a tag to compare

Prepare bump to 0.0.6

0.0.5: Add new state for node disruption

18 Jul 07:47

Choose a tag to compare

Add a state to show that a node disruption is in the middle
of processing.

0.0.3

13 Jul 12:14

Choose a tag to compare

Regen helm chart

0.0.2

07 Jul 15:34

Choose a tag to compare

Disable CGO to build controller

0.0.1: Add code generated for NamespacedName

06 Jul 14:31

Choose a tag to compare

Code generate automatically with make