bypass4netns VS minikube

Socket activation should be the fastest alternative as then there is no need to process and interpret the network traffic that is sent over the socket. Both slirp4netns and netavark process the traffic. If I understand correctly the network driver bypass4netns could have similar performance as socket activation. The current bypass4netns implementation has some security problems but it seems that could be fixed.

(That could a be cool feature)

Also interesting would be to fix the security considerations of using bypass4netns:

"However, it is probably possible to connect to host loopback IPs by exploiting TOCTOU of struct sockaddr * pointers."

There seems to be an implementation idea for how the problem could be fixed:

https://github.com/rootless-containers/bypass4netns/issues/2...

The filesystem performance degradation was resolved in kernel 5.11 which added support for rootless overlayfs.

The network performance is caused by slirp (usermode TCP/IP) but it is being resolved too : https://github.com/rootless-containers/bypass4netns

With the containerized Node.js/Express API, I could run multiple containers, scaling to handle more traffic. Using a tool called minikube, we can easily spin up a local Kubernetes cluster to horizontally scale Docker containers. It was possible to keep one shared instance of the database, and many APIs were routed with an internal Kubernetes load balancer.

Install Minicube - a tool that allows us to spin up a Kubernetes cluster in a local machine Run minikube start to start your Kubernetes cluster Run minikube dashboard to spin up a web-based user interface that allows you to manage your Kubernetes cluster

If you're just messing around, just use kind (https://kind.sigs.k8s.io) or minikube if you want VMs (https://minikube.sigs.k8s.io). Both work on ARM-based platforms.

You can also use k3s; it's hella easy to get started with and it works great.

$ minikube addons enable dashboard 💡 dashboard is an addon maintained by Kubernetes. For any concerns contact minikube on GitHub. You can view the list of minikube maintainers at: https://github.com/kubernetes/minikube/blob/master/OWNERS ▪ Using image docker.io/kubernetesui/dashboard:v2.7.0 ▪ Using image docker.io/kubernetesui/metrics-scraper:v1.0.8 🌟 The 'dashboard' addon is enabled $ minikube addons enable metrics-server 💡 metrics-server is an addon maintained by Kubernetes. For any concerns contact minikube on GitHub. You can view the list of minikube maintainers at: https://github.com/kubernetes/minikube/blob/master/OWNERS ▪ Using image registry.k8s.io/metrics-server/metrics-server:v0.6.4 🌟 The 'metrics-server' addon is enabled $ minikube addons enable ingress 💡 ingress is an addon maintained by Kubernetes. For any concerns contact minikube on GitHub. You can view the list of minikube maintainers at: https://github.com/kubernetes/minikube/blob/master/OWNERS 💡 After the addon is enabled, please run "minikube tunnel" and your ingress resources would be available at "127.0.0.1" ▪ Using image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v20230407 ▪ Using image registry.k8s.io/ingress-nginx/controller:v1.8.1 ▪ Using image registry.k8s.io/ingress-nginx/kube-webhook-certgen:v20230407 🔎 Verifying ingress addon... 🌟 The 'ingress' addon is enabled

A Kubernetes distribution: You need to install a Kubernetes distribution to create the Kubernetes cluster and other necessary resources, such as deployments and services. This tutorial uses kind (v0.18.0), but you can use any other Kubernetes distribution, including minikube or K3s.

3.Minikube ( https://minikube.sigs.k8s.io ):

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES7523fd2c20c7 gcr.io/google\_containers/k8s-dns-sidecar-amd64 "/sidecar --v=2 --..." 18 hours ago Up 18 hours k8s\_sidecar\_kube-dns-86f6f55dd5-qwc6z\_kube-system\_c1333ffc-e4d6-11e7-bccf-0021ccbf0996\_09bd438011406 gcr.io/google\_containers/k8s-dns-dnsmasq-nanny-amd64 "/dnsmasq-nanny -v..." 18 hours ago Up 18 hours k8s\_dnsmasq\_kube-dns-86f6f55dd5-qwc6z\_kube-system\_c1333ffc-e4d6-11e7-bccf-0021ccbf0996\_05c35e00a5a27 gcr.io/google\_containers/k8s-dns-kube-dns-amd64 "/kube-dns --domai..." 18 hours ago Up 18 hours k8s\_kubedns\_kube-dns-86f6f55dd5-qwc6z\_kube-system\_c1333ffc-e4d6-11e7-bccf-0021ccbf0996\_077ef463642b7 gcr.io/google\_containers/pause-amd64:3.0 "/pause" 18 hours ago Up 18 hours k8s\_POD\_kube-dns-86f6f55dd5-qwc6z\_kube-system\_c1333ffc-e4d6-11e7-bccf-0021ccbf0996\_039f618666205 gcr.io/google\_containers/kubernetes-dashboard-amd64 "/dashboard --inse..." 18 hours ago Up 18 hours k8s\_kubernetes-dashboard\_kubernetes-dashboard-vgpjl\_kube-system\_c1176a44-e4d6-11e7-bccf-0021ccbf0996\_0023b7b554a8c gcr.io/google\_containers/pause-amd64:3.0 "/pause" 18 hours ago Up 18 hours k8s\_POD\_kubernetes-dashboard-vgpjl\_kube-system\_c1176a44-e4d6-11e7-bccf-0021ccbf0996\_01c3bdb7bdeb1 gcr.io/google-containers/kube-addon-manager "/opt/kube-addons.sh" 18 hours ago Up 18 hours k8s\_kube-addon-manager\_kube-addon-manager-tpad\_kube-system\_7b19c3ba446df5355649563d32723e4f\_08a00feefa754 gcr.io/google\_containers/pause-amd64:3.0 "/pause" 18 hours ago Up 18 hours k8s\_POD\_kube-addon-manager-tpad\_kube-system\_7b19c3ba446df5355649563d32723e4f\_0b657eab5f6f5 gcr.io/k8s-minikube/storage-provisioner "/storage-provisioner" 18 hours ago Up 18 hours k8s\_storage-provisioner\_storage-provisioner\_kube-system\_c0a8b187-e4d6-11e7-bccf-0021ccbf0996\_067be5cc1dd0d gcr.io/google\_containers/pause-amd64:3.0 "/pause" 18 hours ago Up 18 hours k8s\_POD\_storage-provisioner\_kube-system\_c0a8b187-e4d6-11e7-bccf-0021ccbf0996\_0 I just did the Kubernetes minikube tutorial at https://github.com/kubernetes/minikube, and I cannot stop or remove these containers, they always get recreated.

https://github.com/kubernetes/minikube for local learning that's lightweight.

Haven’t dabbled with minikube yet, but there’s a whole thread about this error here: https://github.com/kubernetes/minikube/issues/9798