MaaS API Key Management Fails with Custom Domain in Red Hat OpenShift AI

Solution Verified - Updated -

Issue

When the MaaS Gateway is configured with a custom domain, the maas-ui container inside the rhods-dashboard pod incorrectly constructs the MaaS API URL using the cluster's default ingress domain (maas.apps.<cluster-domain>) instead of the actual custom Gateway hostname.

As a result, API key management dashboard functionality that relies on the MaaS API is broken.

The API key management view in the Gen AI Studio (RHOAI Dashboard) fails to load, and browser network inspection shows requests being sent to https://maas.apps.<clustername>/maas-api instead of the expected https://<custom-domain>/maas-api.

This issue is always reproducible on any cluster where the MaaS Gateway hostname differs from maas.apps.<cluster-domain>

Environment

  • Red Hat OpenShift AI (RHOAI) 3.4
  • Models as a Service (MaaS) installed and enabled (modelsAsService: Managed in the DataScienceCluster)
  • MaaS Gateway configured with a custom hostname (i.e., the Gateway hostname differs from the default maas.apps.<cluster-domain>)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content