Deploying TwentyCRM on AKS with Kubernetes Manifests
Hello,
I am trying to deploy TwentyCRM on AKS using Kubernetes manifests but have encountered several issues along the way. I followed the instructions provided in the official repository (https://github.com/twentyhq/twenty/tree/main/packages/twenty-docker/k8s) but still haven't managed to get the CRM running successfully.
Here are some of the adjustments I had to make:
Change the path to /k8s/manifests instead of /k8s as mentioned in the documentation.
Remove volumeName from all PVC definitions to avoid errors.
Modify all deployments to set env.value for name: PORT from an integer to a string.
Handle permissions for PostgreSQL by adding an initContainer in deployment-server.yaml to manage permissions on mounted volumes.
Other minor fixes in configurations to align with my AKS environment.
At this point, I have all the resources deployed and running, but the front-end still shows an error:
Unable to Reach Back-end: Response not successful: Received status code 404.
Has anyone managed to deploy TwentyCRM smoothly to AKS and get it running end-to-end? If so, could you share any insights or additional steps that helped and resolved similar issues?
Thanks in advance!
I am trying to deploy TwentyCRM on AKS using Kubernetes manifests but have encountered several issues along the way. I followed the instructions provided in the official repository (https://github.com/twentyhq/twenty/tree/main/packages/twenty-docker/k8s) but still haven't managed to get the CRM running successfully.
Here are some of the adjustments I had to make:
Change the path to /k8s/manifests instead of /k8s as mentioned in the documentation.
Remove volumeName from all PVC definitions to avoid errors.
Modify all deployments to set env.value for name: PORT from an integer to a string.
Handle permissions for PostgreSQL by adding an initContainer in deployment-server.yaml to manage permissions on mounted volumes.
Other minor fixes in configurations to align with my AKS environment.
At this point, I have all the resources deployed and running, but the front-end still shows an error:
Unable to Reach Back-end: Response not successful: Received status code 404.
Has anyone managed to deploy TwentyCRM smoothly to AKS and get it running end-to-end? If so, could you share any insights or additional steps that helped and resolved similar issues?
Thanks in advance!
GitHub
Building a modern alternative to Salesforce, powered by the community. - twentyhq/twenty
