Skip to content

Releases: criteo-forks/opensearch-k8s-operator

v2.4.0-criteo12

25 Jun 05:34

Choose a tag to compare

What's Changed

  • multiple fixes to properly support multi-node scale down operations by @pgoron in #14

Full Changelog: v2.4.0-criteo11...v2.4.0-criteo12

v2.4.0-criteo11

20 Jun 14:16

Choose a tag to compare

What's Changed

  • Revert "Use node/pod IP instead of node name" by @pgoron in #13

Full Changelog: v2.4.0-criteo10...v2.4.0-criteo11

v2.4.0-criteo10

08 Apr 12:16
fa5797e

Choose a tag to compare

What's Changed

  • smartScaler: Check for green status before drain by @damsallem in #11

New Contributors

Full Changelog: v2.4.0-criteo9...v2.4.0-criteo10

v2.4.0-criteo9

18 Nov 16:09

Choose a tag to compare

What's Changed

  • Allow rolling restart of master nodes by @jfwm2 in #10

New Contributors

  • @jfwm2 made their first contribution in #10

Full Changelog: v2.4.0-criteo8...v2.4.0-criteo9

v2.4.0-criteo8

11 Sep 08:55

Choose a tag to compare

What's Changed

  • Add transport certificate renewal by @eappere in #9

Full Changelog: v2.4.0-criteo7...v2.4.0-criteo8

v2.4.0-criteo7

03 Jul 09:13

Choose a tag to compare

What's Changed

  • Use node/pod IP instead of node name by @eappere in #8

Full Changelog: v2.4.0-criteo6...v2.4.0-criteo7

v2.4.0-criteo6

26 Jun 11:48

Choose a tag to compare

What's Changed

  • Fix securityconfig-update job not working at bootstrap time by @pgoron in #6
  • Use eviction to delete pod during rolling upgrade by @pgoron in #7

Full Changelog: v2.4.0-criteo5...v2.4.0-criteo6

v2.4.0-criteo5

29 Jan 14:24

Choose a tag to compare

What's Changed

  • CRITEO - Use RF3 for opendistro security by @geobeau in #5

Full Changelog: v2.4.0-criteo2...v2.4.0-criteo5

v2.4.0-criteo4: CRITEO - Use eviction to delete pod during roll restart

02 Jan 15:23

Choose a tag to compare

The roll restart code is prone to race conditions:
Calling the delete API is fast as it doesn't wait for actual termination
of the pod. The reconciler is called back almost instantly to handle
the other pools. The STS is not yet reporting the change of readiness
of one of the replica, and elasticsearch is not reporting the status as
yellow/red because the pod is not dead yet. So the operator thinks
it's okay to kill another pod.
Fixing the race condition can be done by introducing more checks:

- Using the `CountRunningPodsForNodePool` function, that is
more reliable than checking the status of sts. The status being
eventually consistent. This function list directly the pods.
- Use the Eviction API as it uses Compare And Swap
to ensure consistency with the budget. It can work without PDB
but it might not protect as efficiently against race conditions.

Also added logs to help debug race conditions in the future.

v2.4.0-criteo3

19 Sep 15:40

Choose a tag to compare

CRITEO - Temporarily deactivate PDB management

Can be re-enabled on Kubernetes >= 1.21