release.example.com
where multiple environments would be reachable as serviceA-envA.release.example.com
and serviceB-envA.release.example.com
.*.service-A-envA.release.example.com
and *.staging.example.com
would work. The typical use-case for these environments is for categories or languages, for example, allowing us.staging.example.com
or shoes.qa.example.com
to work.shoes
and the customer is called buyer
and the shopping website is shopping.com
. Then the customer's private application URLs would usually be of the form shoes-buyer.release.shoppping.com
. Custom domains of the form shoes.buyer.com
would need an External DNS configuration as documented in that section.*.release.example.com
) and production or staging environments deployed directly as www.example.com
or staging.example.com
as examples.