Troubleshooting

If your questions are not answered on this page or within the FAQ, please submit a support ticket and our support team will respond as soon as possible!

Solution: Ensure that all required configuration values are properly set in your Helm values file. This includes specifying the database type (Redis) and ensuring your Kubernetes cluster has sufficient resources for the deployment. You can inspect the logs of the failing pods with:

kubectl logs <pod-name>

Solution: Verify that Redis and the Floating Server are deployed in the same namespace and that Redis is reachable from the Floating Server. Check the service definitions and ensure that the Redis service is properly exposing its ports:

Solution: Ensure that a persistent volume claim (PVC) is set up for Redis to store data across restarts. Check your Helm values file to confirm the PVC is defined:

Solution: Make sure that the Kubernetes service for the Floating Server is correctly exposing the port. Use the following command to check the service configuration:

kubectl get svc <floating-server-service>

Ensure that the correct port is exposed and accessible from outside the cluster.