Make sure that the SMI Cluster Deployer is set up and SMI clusters are already deployed. The deployment of SMI clusters facilitates the installation of standalone Cilium CNI and supports various Cilium features and functionalities. For more information on deploying clusters, refer to the SMI documentation.

SMI supports Cilium CNI, which can be installed via the cluster deployer using the following CLI command:

configuration cni type cilium

To enable BGP and BFD CRDs, configure the cluster deployer with the following CLI command:

configuration cilium enable-bgp true

When IsovalentBgpClusterConfig, IsovalentBgpPeerConfig, and IsovalentBgpAdvertisement CRs are created, Cilium deploys BGP routers, creates BGP sessions with configured peers, and advertises or unadvertises service IPs in response to service creation or deletion.

To enable the egress-gateway CRD for stateful and stateless pods, use the following CLI command in the cluster deployer:

configuration cilium enable-egress-gateway true

To configure Cilium’s load balancer algorithm, use the following CLI command:

configuration cilium lb-algorithm { maglev | random }

Note

Although 'maglev' is available as a load balancer algorithm, it is currently recommended to use the 'random' algorithm.

To enable Legacy Host Routing, which is disabled by default, configure the following command:

configuration cilium enable-legacy-host-routing true