Azure Linux Deployment
Good news: Edera installs the same way on Azure Linux as it does on any other Linux distribution.
If you’re running Kubernetes on Azure (whether AKS or self-managed), the standard Edera installation process applies without any Azure-specific modifications.
Prerequisites
The same prerequisites from the Prerequisites section apply:
- Kubernetes cluster running on Azure (AKS or self-managed)
- Node access with root/sudo privileges
- Container runtime (containerd)
Installation Process
Follow the standard installation guide:
The installer will:
- Detect your Azure Linux environment
- Install required dependencies
- Configure the Edera runtime
- Set up the Kubernetes integration
No Azure-specific configuration is required.
Azure-Specific Considerations
Azure Kubernetes Service (AKS)
If you’re running AKS, you can deploy Edera using node pools:
az aks nodepool add \
--resource-group myResourceGroup \
--cluster-name myAKSCluster \
--name ederapool \
--node-count 3 \
--mode UserThen SSH into the nodes and run the Edera installer as described in the Edera Installer guide.
Azure Linux OS
Azure Linux (formerly CBL-Mariner) is Microsoft’s cloud-optimized Linux distribution. Edera fully supports it and works the same as on other distributions:
- Standard package management
- Systemd-based service management
- Containerd runtime integration
Verifying Installation
After installation, verify Edera is working:
# Check Edera service status
sudo systemctl status edera
# Deploy a test workload
kubectl apply -f - <<EOF
apiVersion: v1
kind: Pod
metadata:
name: edera-test-azure
spec:
runtimeClassName: edera
containers:
- name: nginx
image: nginx:latest
EOF
# Verify the pod is running with Edera
kubectl get pod edera-test-azure
kubectl describe pod edera-test-azure | grep "Runtime Class Name"Azure Integration
Edera works seamlessly with Azure-native features:
- Azure CNI: Full compatibility with Azure’s networking
- Azure managed identities: Works with pod-managed identities
- Azure Storage: Supports Azure Disk and Azure Files volumes
- Azure Monitor: Standard Kubernetes monitoring applies
No special configuration needed—Edera operates at the runtime layer without interfering with Azure platform integrations.
Troubleshooting
If you encounter issues specific to Azure:
Check standard Edera logs (covered in Module 5: Troubleshooting)
What’s Next?
Azure deployment is straightforward. Now let’s look at another cloud platform.
Up next: Linode Deployment →
