Self-Hosted-Gateway-V2 custom domain support workaround

Question

Since, we cannot use public domain as per our context, we are using custom domain for integrating APIM and self hosted gateway on private AKS cluster.

During our POC, we observed that there is a limitation from Azure side, that it is not supporting custom domain with Self-Hosted-Gateway-V2.

https://learn.microsoft.com/en-gb/previous-versions/azure/api-management/self-hosted-gateway-migration-guide?tabs=azure-cli#known-limitations

We also tried for a workaound with HostAlias iso custom domain, but no luck.

We are stuck at this point, and not able to move ahead.

https://github.com/Azure/api-management-self-hosted-gateway/issues/164

https://github.com/Azure/api-management-developer-portal/issues/1967

Answer 1

@Rahul Kumar Surati ,

Welcome to the Microsoft Q&A Platform!

So, here's the deal: the self-hosted gateway v2 doesn't support custom domain names yet, which can be a bit of a hassle. When you're trying to integrate Azure API Management (APIM) with a self-hosted gateway on a private AKS cluster, this limitation can cause some issues.

I know you tried using HostAlias as a workaround, but it didn't quite do the trick. Since custom domains aren't supported in the self-hosted gateway v2, your options are a bit limited.

For more solutions or workarounds, check out the official Azure documentation for any updates on this, or take a look at community forums for some alternative tips.

References:

• Self-hosted gateway migration guide
• Guidance for running self-hosted gateway on Kubernetes in production