Classic confinement for microk8s snap

kjackal · May 2, 2018, 10:43am

Hi,

Microk8s is an entire kubernetes cluster in a single snap. We intend to strictly confine the snap but we would like to proceed with testing the classic snap for now.

Thanks,
Konstantinos

jdstrand · May 2, 2018, 12:31pm

We discussed this in person and decided that classic was not needed at this time. If this changes, feel free to request again.

sergiusens · May 6, 2018, 12:49pm

I want to add that we had a discussion to fully move from devmode to strict and it looks promising.

tvansteenburgh · May 11, 2018, 5:17pm

@jdstrand We ended up having to revert to classic for now, due to some hackery needed for killing docker containers created by the snap. The details are here: https://github.com/juju-solutions/microk8s/issues/3. Obviously we will work towards a better solution, but for now we’d like to allow classic so that in the meantime, the snap can be installed from the store.

jdstrand · May 15, 2018, 6:27pm

I’ve verified the publisher and understand the requirements (in fact, I’ll be helping them work towards strict mode). Granting use of classic. This is now live.

Note for this snap to pass manual review you will need to remove all ‘plugs’ and ‘slots’ from your snapcraft.yaml/snap.yaml.

kyrofa · June 10, 2020, 10:25pm

Any progress on this?

jdstrand · June 11, 2020, 8:56pm

Why, yes. We have a kubernetes-support interface and lots of other adjustments for running microk8s and strict mode workers under confinement. Work remains for different workloads and that work is scheduled for this cycle.