aboutsummaryrefslogtreecommitdiffstats
path: root/kubernetes/vfc/charts/vfc-redis/templates/deployment.yaml
diff options
context:
space:
mode:
authoryangyan <yangyanyj@chinamobile.com>2020-03-11 10:14:42 +0800
committeryangyan <yangyanyj@chinamobile.com>2020-03-11 10:15:14 +0800
commit0a90d8df59e2f09d59bff3d9752781f510368dfa (patch)
tree8650c3b1c7fac37e6abb7cba248b20c2256154f7 /kubernetes/vfc/charts/vfc-redis/templates/deployment.yaml
parentb8316cdbeaed1c4929531da836f24639c745ab66 (diff)
Add VFC env about reg_to_msb_when_start to determine whether register to microserice
Becaue now oom can register the microservice to msb automatically, if without K8S, we can also register vfc microservice to msb automatically by vfc container itself. IF it is set to false, vfc contanier will not register again, if it is set to true, vfc will register by itself. we use this flag to determine who is responbile for serice registeration and it can reduce duplicate registration. Change-Id: Ie79a8803725ae0c762d9c39a04f922d9823c46e2 Issue-ID: VFC-1601 Signed-off-by: yangyan <yangyanyj@chinamobile.com>
Diffstat (limited to 'kubernetes/vfc/charts/vfc-redis/templates/deployment.yaml')
-rw-r--r--kubernetes/vfc/charts/vfc-redis/templates/deployment.yaml2
1 files changed, 2 insertions, 0 deletions
diff --git a/kubernetes/vfc/charts/vfc-redis/templates/deployment.yaml b/kubernetes/vfc/charts/vfc-redis/templates/deployment.yaml
index bff1e94766..a6850b5ef2 100644
--- a/kubernetes/vfc/charts/vfc-redis/templates/deployment.yaml
+++ b/kubernetes/vfc/charts/vfc-redis/templates/deployment.yaml
@@ -54,6 +54,8 @@ spec:
env:
- name: MSB_ADDR
value: "{{ .Values.global.config.msbServiceName }}:{{ .Values.global.config.msbPort }}"
+ - name: REG_TO_MSB_WHEN_START
+ value: "{{ .Values.global.config.reg_to_msb_when_start }}"
resources:
{{ include "common.resources" . | indent 12 }}
{{- if .Values.nodeSelector }}