search

LM-Development / aks-sample

Community project providing an undeprecated Microsoft Teams bot sample that runs on Azure Kubernetes Service
https://github.com/LM-Development/aks-sample/tree/main/Samples/PublicSamples/RecordingBot
MIT License
2 stars 0 forks source link

Feature Request: Custom FQDN for cluster #60

Open InDieTasten opened 6 months ago

InDieTasten commented 6 months ago

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

InDieTasten commented 6 months ago

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

InDieTasten commented 6 months ago

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 commented 6 months ago

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 commented 6 months ago

@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 commented 6 months ago

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