Installing Edera on Google Compute Engine (GCE)


ℹ️
Edera deploys as a container runtime which GKE managed-nodes do not support. Edera is fully compatible on GCP nodes and can integrate with any Kubernetes control-plane. See below for more details installing Edera with Kubernetes on GCP.

GCE recommendations

  • Use any Linux distribution except Container-Optimized OS (COS)
  • Works on all GCE instances

Installing Edera on Google Compute Engine follows the same process as any Linux installation.

👉 Start with: Run the Edera installer guide.

Kubernetes integration for GCE

After installing Edera, you’ll need to configure Kubernetes to use Edera’s container runtime interface (CRI) at /var/lib/edera/protect/cri.socket.

New Kubernetes cluster with kubeadm

Initialize your cluster with Edera’s CRI socket:

kubeadm init --cri-socket=unix:///var/lib/edera/protect/cri.socket

For worker nodes:

kubeadm join [control-plane-ip:port] --token [token] --discovery-token-ca-cert-hash [hash] --cri-socket=unix:///var/lib/edera/protect/cri.socket

Existing kubelet configuration

Configure kubelet to use Edera’s CRI socket by adding:

--container-runtime-endpoint=unix:///var/lib/edera/protect/cri.socket

Option 1: Service file

Edit kubelet service:

sudo systemctl edit kubelet

Add:

[Service]
Environment="KUBELET_EXTRA_ARGS=--container-runtime-endpoint=unix:///var/lib/edera/protect/cri.socket"

Option 2: Configuration file

Edit /var/lib/kubelet/config.yaml:

containerRuntimeEndpoint: unix:///var/lib/edera/protect/cri.socket

Important: CLI options take precedence over configuration files. If your kubelet is already configured with --container-runtime-endpoint via command line arguments, remove that option or the configuration file setting will be ignored.

Restart kubelet:

sudo systemctl daemon-reload
sudo systemctl restart kubelet

Important notes

Unsupported environments

Edera does not support k3d, kind, or minikube because they don’t allow CRI socket configuration.

Need help?

Last updated on