apache / apache/openserverless
Health check on the operator restarting if redis breaks
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 576
- Forks
- 29
- Avg merge
- 50m
- Merged PRs (30d)
- 13
Description
- I have searched the issues of this repository and believe that this is not a duplicate.
Ⅰ. Issue Description
Fixing the redis state when resuming docker
Ⅱ. Describe what happened
If you restart the cluster (this happens especially when resuming with docker) REDIS may lose its state, and you need to restart the operator to recreate the proper acls
The solution would be that you put an health check that restarts the operator if redis loses its permissions.
Ⅲ. Describe what you expected to happen
Restarting a machine with docker you should have a cluster working
Ⅳ. How to reproduce it (as minimally and precisely as possible)
Ⅴ. Anything else we need to know?
Merge this PR first to have a single node kind cluster
https://github.com/apache/openserverless-task/pull/169
Ⅵ. Environment:
- K8S Runtime and version:
- OPS CLI version:
- Others:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reproducing a cluster restart or Docker resume and inspect how the operator handles Redis state and permissions; done means the cluster returns to a working state without manually restarting the operator. The linked openserverless-task pull request is identified as a prerequisite.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes, python, redis
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100