Add Helm charts for Vespa multinode HA deployment#1702
Add Helm charts for Vespa multinode HA deployment#1702nikitok wants to merge 1 commit intovespa-engine:masterfrom
Conversation
|
Thanks for the awesome contribution, @nikitok 🙏 We'll look into it and get back to you. |
nikitok
had a problem deploying
to
Vespa Cloud CD
GitHub Actions
Failure
| Values such as `config.serverReplicas`, `services.content.replicas`, and `services.content.storage` can be adjusted in `values.yaml` to match your requirements for scaling and resource configuration. For example: | ||
| ```yaml | ||
| config: | ||
| serverReplicas: 5 |
There was a problem hiding this comment.
| serverReplicas: 5 | |
| serverReplicas: 3 |
Let's keep three as the default number of config servers recommended across all documentation. More than that adds extra operational work, with minimal advantages.
| memory: "1.5G" | ||
| limits: | ||
| memory: "1.5G" |
There was a problem hiding this comment.
Make memory configurable from values for easier override?
| - name: vespa-logs | ||
| mountPath: /opt/vespa/logs | ||
| - name: vespa-workspace | ||
| mountPath: /workspace |
There was a problem hiding this comment.
What is this mount point used for? I can't find any references to it anywhere else in the chart.
| accessModes: [ "ReadWriteOnce" ] | ||
| resources: | ||
| requests: | ||
| storage: 5Gi |
There was a problem hiding this comment.
Make volume claim sizes configurable for easier override?
| - /bin/sh | ||
| - -c | ||
| - | | ||
| until curl -f http://vespa-configserver-0.vespa-internal.vespa.svc.cluster.local:19071/state/v1/health; do |
There was a problem hiding this comment.
Is it possible to get vespa-internal and vespa (namespace) values from the templating functionality to support other values for this without changing the chart?
| done | ||
| containers: | ||
| - name: vespa-admin | ||
| image: vespaengine/vespa |
There was a problem hiding this comment.
Would be nice to support specifying the Vespa version, defaulting to latest.
| requests: | ||
| memory: "1G" | ||
| limits: | ||
| memory: "1G" |
| requests: | ||
| memory: "1.5G" | ||
| limits: | ||
| memory: "1.5G" |
| requests: | ||
| memory: "1.5G" | ||
| limits: | ||
| memory: "1.5G" |
There was a problem hiding this comment.
Make configurable? Memory requirements are very application package and query patterns dependant.
3 participants
Added Helm charts for deployment, based on
Multinode-HA, to allow for more convenient management.Created charts to simplify the deployment of a multi-zone Vespa application.
Architecture of the charts:
configserverwith high-availability support.configserverinitialization, leveraginginitContainers.Added a readiness mechanism for
configserver:These changes simplify the deployment process and ensure the proper sequence for starting components.