support Values.client.resources
This commit is contained in:
parent
71e2fefc62
commit
08ff19831a
2 changed files with 16 additions and 1 deletions
|
@ -99,6 +99,16 @@ spec:
|
|||
name: server
|
||||
- containerPort: 8600
|
||||
name: dns
|
||||
readinessProbe:
|
||||
# NOTE(mitchellh): when our HTTP status endpoints support the
|
||||
# proper status codes, we should switch to that. This is temporary.
|
||||
exec:
|
||||
command:
|
||||
- "/bin/sh"
|
||||
- "-ec"
|
||||
- |
|
||||
curl http://127.0.0.1:8500/v1/status/leader 2>/dev/null | \
|
||||
grep -E '".+"'
|
||||
resources:
|
||||
{{ toYaml .Values.server.resources | indent 12 }}
|
||||
{{ toYaml .Values.client.resources | indent 12 }}
|
||||
{{- end }}
|
||||
|
|
|
@ -68,6 +68,11 @@ client:
|
|||
image: null
|
||||
join: null
|
||||
|
||||
# Resource requests, limits, etc. for the client cluster placement. This
|
||||
# should map directly to the value of the resources field for a PodSpec.
|
||||
# By default no direct resource request is made.
|
||||
resources: {}
|
||||
|
||||
# extraConfig is a raw string of extra configuration to set with the
|
||||
# server. This should be JSON or HCL.
|
||||
extraConfig: |
|
||||
|
|
Loading…
Reference in a new issue