swarmkit VS microk8s

It's supported, though the development pace is rather slow. The are new features (the latest release brought support for the Container Storage Interface) and bugs and issues are worked on by the few maintainers the project has. You can check the repo here: https://github.com/moby/swarmkit

So the thing is support for Swarm was delegated to Mirantis, https://www.mirantis.com/blog/mirantis-will-continue-to-support-and-develop-docker-swarm/ since it was delegated very little was done to move forward swarm _> https://github.com/moby/swarmkit/commits/master , docker swarm itself (docker the company) is deprecated https://github.com/docker-archive/classicswarm . I think because there's no way to monetize swarm there's no real push for new features hence my assumption of deprecation.

Feature request: Enable "--device" in "stack deploy" for Confidential Computing

This doesn't look that abandoned? https://github.com/moby/swarmkit

Or are you talking about swarm the product (versus docker swarm mode)

I don’t feel a momentum in Docker Swarm development, seeing pull requests like #3072 sitting idle for half a year, originally from 2016.

privileged not being supported is problematic, but there are PRs for it on swarmkit, see https://github.com/moby/swarmkit/pull/3072 - let's see if that gets in.

swarm ha placement

It is already in a different repo: moby/swarmkit

Docker Swarm is dead. It should not be used for new projects because the competitive products are much better and more optimal. Check their repo bro - last commit 3months ago. https://github.com/docker/swarmkit https://www.reddit.com/r/docker/comments/ituysl/why_people_are_saying_docker_swarm_is_in_life/ Why would you start a project with a tool which got no future? Let's then use Silverlight or any shit like that.

Mostly it just needs resource defaults merged and some abstract type support so load balancer config doesn't have to be entirely by labels and I would never shift from it.

FROM postgres:11CMD sleep 30 && postgres I'm reusing this example from the same issue with microk8s where I could solve it by changing the kubelet and kubeapi-server configuration files (see https://github.com/ubuntu/microk8s/issues/770 in case you're interested). I assume this is not possible with GKE clusters as they don't expose these files, probably for good reasons.

$ kubectl get podsNAME READY STATUS RESTARTS AGEbackend-deployment-66cff7d4c6-gwbzf 0/1 ImagePullBackOff 0 18s Before that it was ErrImagePull. So, my question is, how to tell it to use local docker images? Somewhere on the internet I read that I need to build images using microk8s.docker but it seems to be removed.

There's a whole community of hobbyists building Raspberry Pi clusters, porting things to work on various Arm processors, exploring and contributing to minimalist distros like k0s and microk8s, etc.

same pvc worked fine on "GKE" (Google Kubernetes Engine) but failing in my local cluster using microk8s

Local Kubernetes Clusters: It is now possible to run Kubernetes on local machines with tools such as Kubernetes in Docker (kind), minikube or MicroK8s. This allows developers to run their first experiments completely isolated from others and with low risk and low cost.

Local Kubernetes clusters are clusters that are running on the individual computer of the developer. There are many tools that provide such an environment, such as Minikube, microk8s, k3s, or kind. While they are not all the same, their use as a development environment is quite comparable.

Since the developer is the only one who has to access this cluster for development, local clusters can be a feasible solution for this purpose. Over time, several solutions have emerged that are particularly made for running Kubernetes in local environments. The most important ones are Kubernetes in Docker (kind), MicroK8s, minikube and k3s. For a comparison of these local Kubernetes options, you can look at this post.

Another very important distinction of this level is that developers have direct access to Kubernetes for the first time. While it is not strictly necessary, the standard case for the Kubernetes access with these tools is to use a local Kubernetes cluster, i.e. a Kubernetes cluster started with tools such as minikube, kind or MicroK8s on the local computer of the developer.