Feature gates
Review the required Gloo versions for gated features that you can optionally enable in the gloo-platform and gloo-platform-crds Helm charts.
In the featureGates Helm setting, you specify a key-value pair, in which the key is the feature name, and the value is a boolean to enable or disable the feature. For example, to configure the insights engine, you set --set featureGates.InsightsConfiguration=true in your helm install command, or set featureGates.InsightsConfiguration to true in your Helm values file. Note that the featureGates section replaces the deprecated experimental section in the gloo-platform Helm chart.
For more information about the Helm chart, see the Helm value reference. For more information about features that are in alpha or beta support, see Solo feature maturity.
For some features, you must enable the feature gate in both the gloo-platform chart and the gloo-platform-crds Helm chart, because the feature requires a specific CRD that is not installed by default. Review the feature description in the following table to check whether the feature gate must be enabled in gloo-platform-crds too.
| Feature | Default value | Maturity | Since | Until | Description | Used by |
|---|---|---|---|---|---|---|
ConfigDistribution | false | Alpha | 2.7.0 | Enables the capability to distribute configuration to connected workload clusters. For example, you can use this feature when creating a multicluster mesh setup to automate peering the service meshes in each cluster. | Gloo management server | |
InsightsConfiguration | false | Alpha | 2.5.0 | 2.9.0 | Configure settings for the insights engine. | Gloo management server |
SafeModeAutoSkipWarming | true | Alpha | 2.6.0 | When this flag is enabled, the Gloo management server automatically excludes workload clusters that were never connected to the management server from Redis safe mode. This setting allows you to seamlessly onboard new clusters without setting the skipWarming field on the corresponding KubernetesCluster resource. NOTE: Enable this field only after you successfully upgraded to 2.6.0 and all workload clusters are reconnected to the Gloo management server and their input snapshots are present in Redis. | Gloo management server | |
StrictRelayLoadBalancing | false | Alpha | 2.12.0 | Fixes a bug in relay server load balancing where the connection count was checked before accounting for the incoming connection. When enabled, this feature enforces stricter 1:1 agent-to-management-pod connections when the number of agents equals the number of management replicas. This ensures optimal load distribution in environments with large numbers of clusters and namespaces. When disabled (default), load balancing uses the previous behavior, which allows slightly more flexibility but might result in uneven distribution. If you require strict 1:1 connections, such as with many clusters and namespaces per cluster, enabling this feature is recommended. If you observed successful failover behavior during pod unavailability with the existing load balancing method, keep this feature disabled. | Gloo management server |