Fix helm installation conflict 60/90760/7
authorKonrad Bańka <k.banka@samsung.com>
Tue, 2 Jul 2019 06:43:11 +0000 (08:43 +0200)
committerKonrad Bańka <k.banka@samsung.com>
Tue, 9 Jul 2019 14:05:23 +0000 (16:05 +0200)
commit7ff99668b98aae1210f72e84fcc1305814563600
treec06ab9617e158076e2677aa17c755ac7af000dd9
parent8445148cf095fcc55a9ada3e2bb0fece7a065089
Fix helm installation conflict

Kubespray installs helm client on kubernetes master. The same client
has to be installed on host running installation playbooks. In single
node scenario, local host already has helm client installed by
kubespray, thus leading to conflict due to way of provisioning.
This helm installation has been moved to global configure playbook, as
well as corrected, not to fail on single host deployments.

Issue-ID: MULTICLOUD-690

Signed-off-by: Konrad Bańka <k.banka@samsung.com>
Change-Id: I1ef779ed0f2fde82758ce9e229c3f5bb015b2aeb
kud/deployment_infra/playbooks/configure-istio.yml
kud/deployment_infra/playbooks/configure-kud.yml