New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Stop processing if pod fail to avoid blocking the CRD #28

Open

leleueri opened this issue Nov 8, 2019 · 0 comments

Contributor

leleueri commented Nov 8, 2019 •

edited

Loading

When a CRD is updated, the DC phase may be blocked in UPDATING is the Elassandra Pods (or Statefulset) can't start du to invalid configuration.

Due to the UPDATING state, a new Update of the CRD has no effect...

To avoid this situation we have to :

keep a CRD copy after a Statefulset becoming RUNNING
watch pod failure (or StatefulSet if the error comes from the STS)
if the post fails to restart (define number of retry) during an UPdate phase:

trigger a rollback of the STS to the previous CRD generation
preserve the failed generationID in CRD status
set the CRD Status in a specific status that requires a SysAdmin action to accept new CRD reconciliation

leleueri changed the title ~~Stop processing if pod fail~~ Stop processing if pod fail to avoid blocking the CRD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment