Helm chart customization
The Helm chart used during installation is flexible and allows for various configurations to fine-tune the UltiHash setup according to your specific needs. Below are key areas where you might want to make changes:
1. Ingress configuration
Purpose: Configure how the UltiHash cluster is accessed externally.
Example: Set up Ingress with specific annotations and TLS configuration.
entrypoint: ingress: host: <your_domain_name> annotations: kubernetes.io/ingress.class: nginx nginx.ingress.kubernetes.io/proxy-body-size: "0" tls: - hosts: - <your_domain_name> secretName: <tls_secret>
Recommendation: Ensure the ingress controller is configured for your environment (e.g., Nginx) and that TLS is used for secure communication.
2. Resource allocation
Purpose: Adjust the resource allocations for service replicas.
Example: Customize resource requests and limits for critical services.
etcd: resources: limits: memory: "2Gi" cpu: "500m" entrypoint: resources: limits: memory: "16Gi" cpu: "8" database: primary: resources: limits: memory: "16Gi" cpu: "8" deduplicator: resources: limits: memory: "64Gi" cpu: "16" storage: resources: limits: memory: "32Gi" cpu: "16"
Recommendation: Adjust resources to balance performance with cost.
Last updated
Was this helpful?