Skip to content
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

Closed
InDieTasten opened this issue May 15, 2024 · 5 comments · Fixed by #85
Closed

Feature Request: Custom FQDN for cluster #60

InDieTasten opened this issue May 15, 2024 · 5 comments · Fixed by #85

Comments

@InDieTasten
Copy link
Member

It would be interesting to have docs on how to deploy with a custom domain.

@InDieTasten
Copy link
Member Author

This would also benefit issues, such as rate-limiting for commonly used azure cloudapps domains for let's encrypt. See #59 for example.

@InDieTasten
Copy link
Member Author

InDieTasten commented May 17, 2024

In general, it doesn't take much to utilize a custom domain.

  1. Have a custom domain with a CNAME towards the built-in domain of the loadbalancer IP (xxxx.{region}.cloudapp.azure.com)
  2. During deployment of the chart, provide the custom domain for the FQDN. (which is the parameter host)
  3. Update Bot Channel Registration in the Azure Bot Resource to use the new custom domain in the Teams Calling URI
  4. Done?

@1fabi0
Copy link
Member

1fabi0 commented May 17, 2024

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.

@InDieTasten
Copy link
Member Author

@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.

@InDieTasten
Copy link
Member Author

InDieTasten commented May 17, 2024

@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 :)

InDieTasten added a commit that referenced this issue Dec 4, 2024
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).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants