Tags: criteo-forks/rook
Tags
[CRITEO] Add Helm chart Release step into criteo workflow
Add extra logs for debugging
Update osd location when Pod location changes If the topology labels on the node hosting the pod are changed, this commit will trigger a redeployment of the osd with the appropriate crush location.
[TEST] Use a specific topology label for test purposes The label is test.topology.rook.io
[CRITEO-BACKPORT]core: set blocking PDB even if no unhealthy PGs appear When `managePodBudgets` is enabled, the Rook operator sets a blocking PDB by considering the failure domains of the OSDs. This functionality is implemented by `reconcilePDBsForOSDs`, and it sets the PDB only after unhealthy PGs appear. However, there are no unhealthy PGs when an OSD with no PGs becomes down. In this case, the PDB is never enabled. This PR makes the operator configure the blocking PDB without waiting for the unhealthy PGs to appear. This PR solves the above problem because the blocking PDB is always enabled when a down OSD is detected. Signed-off-by: Ryotaro Banno <[email protected]>
[BACKPORT][CRITEO] mgr: fix UpdateActiveMgrLabel to retry label updat… …e on failure (#25) fix UpdateActiveMgrLabel to retry label update on failure. Previously, the function always returned the current manager, even if update failed, leading to inconsistent labels. This fix ensures retries on failures. Fixes: rook#13601 (cherry picked from commit ee7c71c) Signed-off-by: Redouane Kachach <[email protected]> Co-authored-by: Redouane Kachach <[email protected]>
PreviousNext