microk8s tends to sneak in breaking changes for the same version, and that's caused a lot of miscellaneous heartbreak for us over time (f18b24d7414e66995e8b1805374ffa86681a9f35 and 46d74feb7a215526ad4b98218745b8ffca076679, for example, on top of a lot of stuff during development). It also doesn't allow us to run several separate clusters in the same environment, which would be useful to us as shipper is a multi-cluster piece of software.
Do note that without microk8s we'll lose its built-in image registry, so addressing #197 is a must before we can do this move.
microk8s tends to sneak in breaking changes for the same version, and that's caused a lot of miscellaneous heartbreak for us over time (f18b24d7414e66995e8b1805374ffa86681a9f35 and 46d74feb7a215526ad4b98218745b8ffca076679, for example, on top of a lot of stuff during development). It also doesn't allow us to run several separate clusters in the same environment, which would be useful to us as shipper is a multi-cluster piece of software.
Do note that without microk8s we'll lose its built-in image registry, so addressing #197 is a must before we can do this move.