[CCSDK] Workaround for naming service host name verification issue 81/125581/1
authorDan Timoney <dtimoney@att.com>
Tue, 26 Oct 2021 14:59:36 +0000 (10:59 -0400)
committerLukasz Rajewski <lukasz.rajewski@orange.com>
Wed, 3 Nov 2021 13:27:31 +0000 (13:27 +0000)
commit0f9e4238361b4971b3c4ef6aab41a4e288e6a010
treec90bc7f90f12936df76fcb07a1f3557d7749a709
parent248e825bc220b9a0ccf37ad6b85ad05a4b7cf342
[CCSDK] Workaround for naming service host name verification issue

The naming service query to policy manager is failing host name
verification.  While this issue is under investigation, it can be
worked around by configuring the naming service to disable host
name verification.  This requires a new version of the network-name-gen
microservice (1.2.1), and a change to set a new env variable to
disable host name verification (enabled by default if this variable
is unset).

Issue-ID: CCSDK-3501
Signed-off-by: Dan Timoney <dtimoney@att.com>
Change-Id: Ia471cd27ce16b6e79a3ce6708e08c7d5f239feb3
(cherry picked from commit 7ec6cb6b34221a9a2293fbc3c09a89940c8f18bd)
kubernetes/common/network-name-gen/templates/deployment.yaml
kubernetes/common/network-name-gen/values.yaml