3
Helm chart for Kubernetes
Source: twentyhq/twenty#8900 · opened by @shairozan
Summary The manifests were a good starting point, but there's a lot of variances that need to be accommodated for: • NGINX as an ingress controller won't be everyone's preferred. Most people default to the K8s native ingress controller * This is because most cloud integrations (ACM Certificates in AWS, DNS Integration) etc work via annotations on the controller • Users should have the option to either run the DB in K8s or just provide a connection string • Users should have the option to either run redis in K8s or just provide a connection • Scaling a resiliency should be an option • I still need to verify if the requests / limits are appropriate to avoid memory pressure termination of the services • The option of using NFS file systems for the docker-data and the server-data volumes should be an option * If that's not used, and a volume from a PVC is used, an init container should be added to the server to ch…
No pledges yet. Be the first to back this.
Comments
Similar requests
[Helm] Publish the chart to a public Helm repository
2 votes · 0 comments
Details in a Gannt type timeline display
4 votes · 0 comments
Feature: allow setting a Dashboard as the default landing page (post-login home)
3 votes · 0 comments
Column-footer aggregates (Sum/Min/Max/Avg) should follow the field's Short/Full format
1 vote · 0 comments
No comments yet.