virtink VS etcd

$ kubectl apply -f https://github.com/smartxworks/virtink/releases/download/v0.11.0/virtink.yaml  ✔   namespace/virtink-system created customresourcedefinition.apiextensions.k8s.io/virtualmachinemigrations.virt.virtink.smartx.com created customresourcedefinition.apiextensions.k8s.io/virtualmachines.virt.virtink.smartx.com created serviceaccount/virt-controller created serviceaccount/virt-daemon created clusterrole.rbac.authorization.k8s.io/virt-controller created clusterrole.rbac.authorization.k8s.io/virt-daemon created clusterrolebinding.rbac.authorization.k8s.io/virt-controller created clusterrolebinding.rbac.authorization.k8s.io/virt-daemon created service/virt-controller created deployment.apps/virt-controller created daemonset.apps/virt-daemon created certificate.cert-manager.io/virt-controller-cert created certificate.cert-manager.io/virt-daemon-cert created issuer.cert-manager.io/virt-controller-cert-issuer created issuer.cert-manager.io/virt-daemon-cert-issuer created mutatingwebhookconfiguration.admissionregistration.k8s.io/virtink-mutating-webhook-configuration created validatingwebhookconfiguration.admissionregistration.k8s.io/virtink-validating-webhook-configuration created $ kubectl get po,svc -A  ✔  NAMESPACE NAME READY STATUS RESTARTS AGE kube-system pod/local-path-provisioner-7b7dc8d6f5-8cwd8 1/1 Running 0 10m kube-system pod/coredns-b96499967-cc7fw 1/1 Running 0 10m kube-system pod/svclb-traefik-baea9d36-vjxzg 2/2 Running 0 10m kube-system pod/helm-install-traefik-crd-ghbn2 0/1 Completed 0 10m kube-system pod/svclb-traefik-baea9d36-2vw6x 2/2 Running 0 10m kube-system pod/helm-install-traefik-fc9xw 0/1 Completed 1 10m kube-system pod/svclb-traefik-baea9d36-g42x2 2/2 Running 0 10m kube-system pod/traefik-56cfcbb99f-5qgvd 1/1 Running 0 10m kube-system pod/metrics-server-84f8d4c4fc-wx8bl 1/1 Running 0 10m cert-manager pod/cert-manager-cainjector-5987875fc7-g94ft 1/1 Running 0 2m58s cert-manager pod/cert-manager-6dd9658548-slxrp 1/1 Running 0 2m58s cert-manager pod/cert-manager-webhook-7b4c5f579b-76x57 1/1 Running 0 2m58s virtink-system pod/virt-daemon-dv9m9 1/1 Running 0 41s virtink-system pod/virt-daemon-mv994 1/1 Running 0 41s virtink-system pod/virt-controller-768b979d4-gzlzt 1/1 Running 0 41s virtink-system pod/virt-daemon-jpz87 1/1 Running 0 41s NAMESPACE NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE default service/kubernetes ClusterIP 10.43.0.1 443/TCP 11m kube-system service/kube-dns ClusterIP 10.43.0.10 53/UDP,53/TCP,9153/TCP 11m kube-system service/metrics-server ClusterIP 10.43.21.66 443/TCP 10m kube-system service/traefik LoadBalancer 10.43.170.138 174.138.1.202,188.166.109.175,188.166.88.194 80:32630/TCP,443:30841/TCP 10m cert-manager service/cert-manager ClusterIP 10.43.182.103 9402/TCP 2m59s cert-manager service/cert-manager-webhook ClusterIP 10.43.136.111 443/TCP 2m58s virtink-system service/virt-controller ClusterIP 10.43.196.10 443/TCP 42s

Virtink is a Kubernetes add-on for running Cloud Hypervisor virtual machines. By using Cloud Hypervisor as the underlying hypervisor, Virtink enables a lightweight and secure way to run fully virtualized workloads in a canonical Kubernetes cluster.

sudo dnf -y install curl wget vim ETCD_RELEASE=$(curl -s https://api.github.com/repos/etcd-io/etcd/releases/latest|grep tag_name | cut -d '"' -f 4) echo $ETCD_RELEASE wget https://github.com/etcd-io/etcd/releases/download/${ETCD_RELEASE}/etcd-${ETCD_RELEASE}-linux-amd64.tar.gz tar xvf etcd-${ETCD_RELEASE}-linux-amd64.tar.gz cd etcd-${ETCD_RELEASE}-linux-amd64 sudo mv etcd* /usr/local/bin ls /usr/local/bin /usr/local/bin/etcd --version

Reading the standard library will give you ideas/insight about various Go idiomatic patterns/approaches, and you can see a full website/API implementation in the pkg.go.dev repository (https://github.com/golang/pkgsite). Projects like https://github.com/etcd-io/etcd may be interesting too.

Failure Detection and Recovery It’s not enough to have backup systems. It’s also crucial to detect failures quickly. Modern systems employ monitoring tools and rely on distributed coordination systems such as Zookeeper or etcd to identify faults in real-time: once detected, recovery mechanisms are triggered to restore the service.

Service Discovery: Microservices need to discover and communicate with each other dynamically. Service discovery tools like etcd, Consul, or Kubernetes built-in service discovery mechanisms help locate and connect to microservices running on different nodes within the infrastructure.

APISIX uses etcd to store and synchronize configurations.

etcd is an excellent key-value distributed database used internally by Kubernetes and managed by the CNCF. It's a great option, and that's the reason why Apache APISIX uses it too. Yet, it's not devoid of issues.

Someone on HN (https://news.ycombinator.com/item?id=36682595) suggested etcd (https://etcd.io)

In traditional mode, APISIX stores its configuration in etcd. APISIX offers a rich API to access and update the configuration, the Admin API. In standalone mode, the configuration is just plain YAML. It's the approach for GitOps practitioners: you'd store your configuration in a Git repo, watch it via your favorite tool (e.g., Argo CD or Tekton), and the latter would propagate the changes to APISIX nodes upon changes. APISIX reloads its configuration every second or so.

I am not sure neither. But this might overcome the etcd's soft storage limit of 8GB? [1]

[1] https://github.com/etcd-io/etcd/issues/9771