Releases: criteo-forks/opensearch-k8s-operator
Releases · criteo-forks/opensearch-k8s-operator
v2.4.0-criteo9
v2.4.0-criteo8
What's Changed
Full Changelog: v2.4.0-criteo7...v2.4.0-criteo8
v2.4.0-criteo7
What's Changed
Full Changelog: v2.4.0-criteo6...v2.4.0-criteo7
v2.4.0-criteo6
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
What's Changed
Full Changelog: v2.4.0-criteo2...v2.4.0-criteo5
v2.4.0-criteo4: CRITEO - Use eviction to delete pod during roll restart
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
CRITEO - Temporarily deactivate PDB management Can be re-enabled on Kubernetes >= 1.21
v2.4.0-criteo2
CRITEO - Temporarily deactivate PDB management Can be re-enabled on Kubernetes >= 1.21
v2.4.0-criteo1
CRITEO - Delete existing workflows and create criteo customized workflow
v2.3.1-criteo10
CRITEO - Use built in java truststore for securityadmin.sh