- K8s, MicroK8s and Netmaker
| Type | Limitation | Solution |
|---|---|---|
| Etcd | It is the brain of your cluster and is not latency tolerant. | MicroK8s |
| Networking | Nodes need to be able to talk to each other directly and securely. | Netmaker |
| Latency | High latency is unacceptable for enterprise applications. | Netmaker |
MicroK8s
- Automatic, autonomous and self-healing HA
- MicroK8s supports high availability using Dqlite as the datastore for cluster state. Dqlite is a fast, embedded, persistent SQL database that is perfect for fault-tolerant IoT devices and micro clouds.
- If the datastore loses one of its nodes. The automatic promotion of standby nodes into the voting cluster of Dqlite makes MicroK8s HA autonomous and ensures that quorum is maintained even if no administrative action is taken.
- HA MicroK8s provides API services on all nodes. This means that any node in the cluster can be a target for kubectl. Administrators can perform tasks on any node.
- There is no differentiate between masters and workers. That's because in MicroK8s, every node has a copy of the control plane, so there really isn't a distinction.
Netmaker If you have at least two machines with internet access that you need to connect with a secure tunnel, Netmaker is for you. If you have thousands of servers spread across multiple locations, data centers, or clouds, Netmaker is also for you.
- Netmaker is easy to integrate with Kubernetes and creates flat, secure networks over WireGuard for nodes to talk over.
- Netmaker is faster because it uses kernel WireGuard. It is more dynamic because the server and agents are fully configurable
- Google - Anthos
- K8s federation
-
Juju
-
porter.sh
