Yeah, your approach makes sense and AFAIK should work. We don't test on clustered lxd right now, but I'd like to see this work - I'm not aware of any reasons why it wouldn't.
But, the juju-kubernetes profiles you show above are not correct, so that's a problem. Did your steps looks roughly like this?
1. After you bootstrap, do `juju add-model kubernetes`
2. Using the instructions on the wiki you cited, apply the custom profile on all 5 hosts, ensuring that $JUJU_MODEL is "kubernetes".
3. juju deploy cs:bundle/canonical-kubernetes-592
Yeah, your approach makes sense and AFAIK should work. We don't test on clustered lxd right now, but I'd like to see this work - I'm not aware of any reasons why it wouldn't.
But, the juju-kubernetes profiles you show above are not correct, so that's a problem. Did your steps looks roughly like this?
1. After you bootstrap, do `juju add-model kubernetes` canonical- kubernetes- 592
2. Using the instructions on the wiki you cited, apply the custom profile on all 5 hosts, ensuring that $JUJU_MODEL is "kubernetes".
3. juju deploy cs:bundle/
This will get easier in the future, once this feature is done: https:/ /bugs.launchpad .net/charm- kubernetes- master/ +bug/1835078
As for alternatives, you could also explore using the KVM Pods feature of MAAS: https:/ /docs.maas. io/2.6/ en/manage- kvm-intro