Closed deshneni-akhil closed 2 weeks ago
The sample needs an additional TCP port for ingoing Traffic. This means the whole sample does not work in an Azure App Service, so if you somehow to manage to embed the certificate in you're container or load the certificate from an external source like an Azure Key Vault. You will fail at the startup of the container or when trying to do calls as the Media Platform will try to establish a TCP connection with you're bot which the Azure App Service won't allow and Won't let you configure. It's more likely that you can run the recording bot as an Azure Container Instance. I think Azure Container Apps also only allows HTTP/HTTPS traffic to the containers.
Closing this as the desired deployment is not possible and the tutorial is explicitly made for working with AKS.
Describe the issue I am using this tutorial to build and deploy the RecordingBot service to Azure https://github.com/LM-Development/aks-sample/blob/main/Samples/PublicSamples/RecordingBot/docs/tutorials/deploy-tutorial.md
We have decided to use Azure App Service to deploy the ACR container, the container has been successfully integrated with APP service however when I look into endpoint I am receiving a 502 deep-diving into the code and executing entry point script I observe the following behavior.
Logs
Additional context
I am not able to execute the 5th step in the document https://github.com/LM-Development/aks-sample/blob/main/Samples/PublicSamples/RecordingBot/docs/tutorials/deploy/5-helm.md where it involves using helm and kubectl to deploy the certificate to AKS. I am looking for an approach where I can upload the custom certificate(.ppk) file from local environment via docker essentially looking for a path to bypass the 5th step to resolve the above issue.
Using certbot I have obtained .ppk file for custom domain
Please let me know your thoughts on how I can resolve this issue any help is appreciated.