Best practices for running Apache Answer on Kubernetes

Viewed 9

We’re using Apache Answer at my company and are evaluating how to best deploy and scale it in a Kubernetes environment. I couldn’t find official documentation or community guidance specific to Kubernetes, so I’d like to ask a few questions:

Does it make sense to use a shared PersistentVolumeClaim (PVC) between pods for cache directory?

Is horizontal scaling supported or recommended, and are there known limitations?

We’ve observed that occasionally the pod gets restarted due to readiness/liveness probe timeouts, even though CPU and memory usage are low and logs show normal activity as if the app were responsive. Has anyone else experienced this behavior?

1 Answers

There may be a need for not just shared caches, but also for uploading files as well. Of course, if you need to scale horizontally, it might be better to use the S3 plugin to store files and use the redis plugin for cache. We also have instances of Apache Answer deployed in k8s environments, and everything is fine, no readiness/liveness timeouts.