Gateway API support for Embedded Container Service

Gateway API support is introduced for Cloudera Embedded Container Service clusters, supporting both TLS- and non-TLS-enabled Cloudera AI workbenches in Cloudera AI on premises 1.5.5 SP2.

By default, Gateway API routing remains disabled in Cloudera AI on premises 1.5.5 SP2 and higher releases but can be enabled for Cloudera AI by adding an EnableGatewayAPI entry to the mlx_configuration table using the following command:

kubectl exec -it cdp-embedded-db-0 -n cdp -c cdp-cdp-embedded-db -- /bin/bash
psql
\c db-mlx
UPDATE mlx_configuration SET variable_value = true WHERE variable_name = 'EnableGatewayAPI';

Restricted application subdomain names when creating Gateway API

Do not use the subdomain names listed in Restricted application subdomain names and the following subdomain names when creating Gateway API.
  • Existing subdomain names

    Existing applications that use one of the restricted subdomains, for example, rest or modelservice might conflict with the subdomain names of platform listeners during the migration from Ingress to Gateway API XListenerSets/HTTPRoutes.