Get the kubeconfig credentials from MongoDB 11/9611/1
authorDavid Garcia <david.garcia@canonical.com>
Wed, 22 Jul 2020 15:56:12 +0000 (17:56 +0200)
committerDavid Garcia <david.garcia@canonical.com>
Thu, 20 Aug 2020 09:47:32 +0000 (11:47 +0200)
commit2c791b34626ff76ab1886a110599998f9de0df80
tree364c1e3aecba8011fe6e01d12e71d0388c10b88d
parent84ebb751f36f724b6ddd7d9925e43534b2420ab2
Get the kubeconfig credentials from MongoDB

This the previous approach, the kubeconfig was gotten from the filesystem,
which has issues scaling the LCM, because the kubeconfig was only present
in the pod that had initialized the environment.

The kubeconfig is stored in Mongo, and this commit basically gets the config from there, so it doesn't matter which LCM needs access to it.

Change-Id: I80458db5124122a4b7b3eb3a9b00cb4a4add11ff
Signed-off-by: David Garcia <david.garcia@canonical.com>
n2vc/k8s_juju_conn.py