k8s: Resolve address conflicts in virtual environments 16/96416/1
authorPawel Wieczorek <p.wieczorek2@samsung.com>
Mon, 30 Sep 2019 12:23:30 +0000 (14:23 +0200)
committerPawel Wieczorek <p.wieczorek2@samsung.com>
Mon, 30 Sep 2019 13:31:13 +0000 (15:31 +0200)
commit155417479ebc5c531349dd898b96ef4a819b0f0a
treeb309fa341d08cf5ebb89c943afeaa476d09a3d7c
parentbd12bfbc6fbe4ecfc2152467ea6785c9e5163763
k8s: Resolve address conflicts in virtual environments

Running Casablanca and Dublin virtual environments at the same time led
to networking issues - the same IP had been assigned to cluster nodes.

Issue-ID: SECCOM-235
Change-Id: I2a59d023115326f5b132782a32190fd8f7dc1f48
Signed-off-by: Pawel Wieczorek <p.wieczorek2@samsung.com>
test/security/k8s/vagrant/casablanca/Vagrantfile
test/security/k8s/vagrant/dublin/Vagrantfile
test/security/k8s/vagrant/dublin/cluster.yml