Embed lxd profile in charm
Bug #1835078 reported by
Tim Van Steenburgh
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Kubernetes Control Plane Charm |
Fix Released
|
Wishlist
|
Peter Jose De Sousa | ||
Kubernetes Worker Charm |
Fix Released
|
Wishlist
|
Peter Jose De Sousa |
Bug Description
If charm embeds a lxd profile, Juju will apply it: https:/
Use this feature to apply the profile we need for Charmed Kubernetes: https:/
Our profiles has keys that aren't allowed by Juju except by using the --force flag. It's okay to require --force for now - maybe we can clean up the profile later so that --force isn't necessary.
Changed in charm-kubernetes-master: | |
importance: | Undecided → Wishlist |
assignee: | nobody → Tim Van Steenburgh (tvansteenburgh) |
assignee: | Tim Van Steenburgh (tvansteenburgh) → Peter De Sousa (pjds) |
Changed in charm-kubernetes-worker: | |
importance: | Undecided → Wishlist |
assignee: | nobody → Peter De Sousa (pjds) |
Changed in charm-kubernetes-worker: | |
status: | New → In Progress |
Changed in charm-kubernetes-master: | |
status: | New → In Progress |
Changed in charm-kubernetes-master: | |
status: | Fix Committed → Fix Released |
Changed in charm-kubernetes-worker: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This is a neat idea. One challenge I've found today was that Vault locker in Kubernetes master required an unused loopback device.
LXD itself supports creating a loopback device for a container like:
loop-control:
path: /dev/loop-control
type: unix-char
loop0:
path: /dev/loop0
type: unix-block
But to go through this code block is still tricky: /github. com/juju- solutions/ layer-vaultlock er/blob/ 7e3d485c6f7507a bf3667381c95ba6 1b85bdfa76/ lib/charms/ layer/vaultlock er.py#L166- L184
https:/