Ⅰ. 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
apache/openserverless-task#169
Ⅵ. Environment:
- K8S Runtime and version:
- OPS CLI version:
- Others:
Ⅰ. 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
apache/openserverless-task#169
Ⅵ. Environment: