Deployment modes

Choose whether you want to deploy Gloo Network for Cilium in one cluster, or across multiple clusters.

Single cluster mode

Gloo Network for Cilium is fully functional when the control plane (management server) and data plane (agent and workloads) both run within the same cluster. You can easily install both the control and data plane components by using one installation process. If you choose to install the components in separate processes, ensure that you use the same name for the cluster during both processes.

Multicluster mode

A multicluster Gloo Network for Cilium setup consists of one management cluster that you install the Gloo control plane (management server) in, and one or more workload clusters that serve as the data plane (agent and workloads). By running the control plane in a dedicated management cluster, you can ensure that no workload pods consume cluster resources that might impede management processes. Many guides throughout the documentation use one management cluster and two workload clusters as an example setup.

Sidecar deployment options

You can deploy some Gloo components as either standalone pods or as sidecar containers to other component pods. Deploying components as sidecars can help reduce the amount of compute resources required to run Gloo Network.

The following components can be deployed either as standalone pods or as sidecars. For more information about the installed components, review the Gloo Network for Cilium architecture.

Component deployed as a sidecarMain component podInstallation setting
Gloo agentGloo management serverglooAgent.runAsSidecar: true
Note that the agent is available as a sidecar only in single-cluster environments.
Gloo insights engineGloo management serverglooInsightsEngine.runAsSidecar: true
Gloo analyzer
  • Single cluster: Gloo management server
  • Multicluster: Gloo agent
glooAnalyzer.runAsSidecar: true

Installation methods

After you decide on a single or multicluster environment, choose whether to use the meshctl CLI or Helm charts to install Gloo Network.

CLI install profiles

Gloo packages profiles in the meshctl CLI for quick Gloo Network installations. Profiles provide basic Helm settings for a minimum installation, and are suitable for testing setups. Because the profiles provide standard setups, they can also be useful starting points for building a customized and robust set of Helm installation values.

In your meshctl install and meshctl cluster register commands, you can specify a Gloo Network profile in the --profiles flag. Note that any values you specify in --set flags have highest merge priority.

ProfileUse caseDeployed components
gloo-core-single-clusterInstall all Gloo Network components into a single-cluster Kubernetes setup.Gloo management server, Gloo UI, Gloo insights engine, Gloo OpenTelemetry (OTel) gateway, Gloo agent, Gloo analyzer, Gloo OTel collector agents, Prometheus, Redis
gloo-core-mgmtIn a multicluster Kubernetes setup, install the Gloo Network control plane in a dedicated cluster.Gloo management server, Gloo UI, Gloo insights engine, Gloo OTel gateway, Prometheus, Redis
gloo-core-agentIn a multicluster Kubernetes setup, register a workload cluster with the control plane.Gloo agent, Gloo analyzer, Gloo OTel collector agents
cilium-flowsIf you install the Solo distribution of the Cilium CNI in your cluster, enable Cilium pod logs collection in the Gloo telemetry collector agent. For more information, see Add Cilium flow logs.

To set up Gloo Network with these profiles, see the quickstart guide.

Helm charts

To extensively customize the settings of your Gloo Network installation, you can use the gloo-platform and gloo-platform-crds Helm charts.

Installation Helm chart

All components for a full Gloo Network for Cilium installation are available in the gloo-platform Helm chart.

You can see all possible fields that you can set for the chart by running the following command.

  helm show values gloo-platform/gloo-platform --version v2.5.0 > all-values.yaml
  

For more information about each field, see the Helm values documentation. To set up Gloo Network with Helm, see the advanced installation guide.

CRD Helm chart

All CRDs that are required for a Gloo Network installation are available in the gloo-platform-crds Helm chart.

By default, this Helm chart installs all CRDs that are available in Gloo Platform, including CRDs that you can use only if you have a Gloo Mesh Enterprise or Gloo Mesh Gateway license. To install only the CRDs that are relevant to Gloo Network, set installEnterpriseCrds to false. To see all CRD installation options, see the Helm values documentation.

When you set installEnterpriseCrds to false, the following CRDs are installed:

  certificaterequests.internal.gloo.solo.io
dashboards.admin.gloo.solo.io
discoveredcnis.internal.gloo.solo.io
discoveredgateways.internal.gloo.solo.io
gatewaylifecyclemanagers.admin.gloo.solo.io
issuedcertificates.internal.gloo.solo.io
istiolifecyclemanagers.admin.gloo.solo.io
kubernetesclusters.admin.gloo.solo.io
meshes.internal.gloo.solo.io
podbouncedirectives.internal.gloo.solo.io
workspaces.admin.gloo.solo.io
workspacesettings.admin.gloo.solo.io
xdsconfigs.internal.gloo.solo.io
  

If you already installed the chart, you can run kubectl get crds -A | grep gloo.solo.io to see the installed CRDs.