-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Custom FQDN for cluster #60
Comments
This would also benefit issues, such as rate-limiting for commonly used azure cloudapps domains for let's encrypt. See #59 for example. |
In general, it doesn't take much to utilize a custom domain.
|
How to describe a Setup for multiple DNS providers hundreds of dns providers have quoite a lot of ways to setup DNS entrys. This makes it quite difficult for starters, either they need the same DNS provider as in an example or they already need to know how to do the setup. |
@1fabi0 I don't think we need to explain how to setup the CNAME record. But the steps 1-3 I described could be part of the docs. It just needs to be verified, that these steps are all that is necessary to get a custom domain to work. Maybe I forgot something. |
@osamabinsaleem if you go this route, please let us know if it works and if there were any steps missing. Then we would include these in the docs in the future :) |
Fixes #60 Add documentation for deploying with a custom domain. --- For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/LM-Development/aks-sample/issues/60?shareId=XXXX-XXXX-XXXX-XXXX).
It would be interesting to have docs on how to deploy with a custom domain.
The text was updated successfully, but these errors were encountered: