GitHub user prashanthr2 edited a comment on the discussion: CKS Enhancements -
Custom CNI Documentation
@jdhirst As mentioned by @kiranchavala the failure when using example calico
CNI could be as a result of missing Routed Network and BGP config.
Here is a sample configuration for the Cilium CNI network you were looking for.
I tested this in my lab environment and was able to successfully deploy a CKS
cluster. This configuration uses the VXLAN overlay mode for pod networking. As
you can see, I have hardcoded the cilium version
Please treat this as a reference only. The configuration may require
adjustments based on your environment, Kubernetes version, and operational
constraints. You should thoroughly test in a non-production setup before
rolling it out in production, as CNI changes can directly affect cluster
networking and workload availability.
```
- |
cat >/home/cloud/cilium-install.sh <<'EOF'
#!/bin/bash
set -ex
export KUBECONFIG=/etc/kubernetes/admin.conf
export PATH=$PATH:/opt/bin:/usr/local/bin
export HOME=/root # fix for cilium cache issue
# Wait until kube-apiserver is ready
until kubectl get nodes >/dev/null 2>&1; do
echo "Waiting for kube-apiserver..."
sleep 5
done
# Install cilium-cli
curl -L --remote-name-all
https://github.com/cilium/cilium-cli/releases/latest/download/cilium-linux-amd64.tar.gz
tar xzf cilium-linux-amd64.tar.gz
mv cilium /usr/local/bin/cilium
# Deploy Cilium
cilium install --version 1.18.2 --wait
cilium status --wait
EOF
- chmod +x /home/cloud/cilium-install.sh
- /home/cloud/cilium-install.sh || true
```
GitHub link:
https://github.com/apache/cloudstack/discussions/11692#discussioncomment-14510535
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
