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 use Istio in ambient mode with Gloo Mesh Gateway, you set --set featureGates.AmbientMode=true in your helm install command, or set featureGates.AmbientMode 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 Gloo feature maturity.

FeatureDefault valueMaturitySinceUntilDescriptionUsed by
EnableJWTPolicyEastWestRoutetrueGA2.5.4Enables JWTPolicies to apply to selected east-west routes when configuring applyToRoutes API.Gloo management server
GatewayDefaultDenyAllHTTPRequestsfalseGA2.5.0In Gloo Mesh Gateway, apply external auth or JWT policies to enable traffic for specific routes. This feature ensures ongoing security, even in the event of errors like policy deletion or Envoy filter issues. By default, all existing routes bypass this mechanism. To onboard routes to this new feature, you must label your HTTP routes with the reserved 'gateway.gloo.solo.io/require_auth': 'true' label. Once labeled, routes become subject to the dynamic default deny behavior, reinforcing security.Gloo management server
InsightsConfigurationfalseAlpha2.5.0Configure settings for the insights engine.Gloo management server
ReconcilerRelationshipWritestrueAlpha2.5.0Allow the Gloo reconciler, which applies translated Gloo resources in your workload clusters, to track relationships between input and output resources. Disabling this feature can improve system performance.Gloo management server