Adam Stokes

The thought here is that you run `~/bin/kubect.JUJU_MODEL` so that you always get the correct cluster for whatever model you are inspecting. Are you saying this is not happening?

Ok, can we discuss the best course of action to handle this in our spells? Bring in @marcoceppi, @chuckbutler , @johnsca for more input

First question I have is: Should we be merging all configs into a single ~/.kube/config file?

@mbruzek ok this sounds good, I think we can use the same naming convention that we do now fo r the separate files and just clean those up on a...

> There are some implications, however, since we can't just use the model name as it's usually over 35 characters long (that is woefully long to hand type every time...

not yet, it's on my todo

Mind posting links where I can learn about its installation requirements etc?

So we do modify the lxd profile to allow certain kernel modules in to the containers. Do we just need the zfs modules loaded? I can easily add those in...

You can try updating the profile: ``` lxc profile edit juju-f96834-9 ``` And adding the necessary kernel modules to `linux.kernel_modules:` if you need access to `/proc` as well in that...

Heres a list of default modules loaded when installing zfsutils-linux: ``` zfs 2813952 3 zunicode 331776 1 zfs zcommon 57344 1 zfs znvpair 90112 2 zfs,zcommon spl 102400 3 zfs,zcommon,znvpair...