From 0a90d8df59e2f09d59bff3d9752781f510368dfa Mon Sep 17 00:00:00 2001 From: yangyan Date: Wed, 11 Mar 2020 10:14:42 +0800 Subject: 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 --- kubernetes/vfc/values.yaml | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'kubernetes/vfc/values.yaml') diff --git a/kubernetes/vfc/values.yaml b/kubernetes/vfc/values.yaml index 88275aea83..b204c58f94 100644 --- a/kubernetes/vfc/values.yaml +++ b/kubernetes/vfc/values.yaml @@ -20,6 +20,11 @@ global: msbPort: 443 redisServiceName: vfc-redis redisPort: 6379 +# Becaue now oom can register the microservice to msb automatically, +# 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. reg_to_msb_when_start: False mariadb_admin: root persistence: -- cgit 1.2.3-korg