Troubleshooting

if your questions are not answered on this page or within the docid\ z 8rl9s34hqouka58a23h , please https //licensespring zendesk com/hc/en us/requests/new and our support team will respond as soon as possible! issue helm chart deployment fails 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> issue redis not connecting to floating server 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 ports \ port 6379 issue data not persisting in redis 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 persistence enabled true storageclass \<your storage class> accessmodes \ readwriteonce size 1gi issue floating server not accessible 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