This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 96%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ENJ%3C/text%3E%3C/svg%3E)
kubectl get pods -n teams-recording-bot
output:
NAME READY STATUS RESTARTS AGE
teams-recording-bot-0 0/1 ContainerCreating 0 42m
can't setup certifcates:
kubectl get cert -n teams-recording-bot
NAME READY SECRET AGE
ingress-tls False ingress-tls 41m
kubectl logs -n teams-recording-bot teams-recording-bot-0
Error from server (BadRequest): container "recording-bot" in pod "teams-recording-bot-0" is waiting to start: ContainerCreating
pod logs:
[Pod] [teams-recording-bot-0] FailedMount: Unable to attach or mount volumes: unmounted volumes=[certificate], unattached volumes=[kube-api-access-bnvqt certificate]: timed out waiting for the condition
11 mins ago [Pod] [teams-recording-bot-0] FailedMount: Unable to attach or mount volumes: unmounted volumes=[certificate], unattached volumes=[certificate kube-api-access-bnvqt]: timed out waiting for the condition
1 min ago [Pod] [teams-recording-bot-0] FailedMount: MountVolume.SetUp failed for volume "certificate" : secret "ingress-tls" not found
682 msecs ago [Pod] [teams-recording-bot-0] Scheduled: Successfully assigned teams-recording-bot/teams-recording-bot-0 to aksscale000000
Hello @Nikheel Jain
I hope you are doing fine.
I would like to provide my humble opinion on this case scenario.
Furthermore, there is a good point to be shared as shown below:
Use one bot channel registration per environment, since your endpoint changes when you switch between local development, staging, and production environments.
Deleting the Teams channel registration will cause a new pair of keys to be generated when it is re-enabled. This invalidates all 29:xxx and a:xxx IDs that the bot may have stored for proactive messaging.
I hope this can help you the behavior observed until now buddy : )
Looking forward to your feedback,
Best Regards,
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
Apologies for the delay in responding.
I have read through this requirements doc of the media bot to get an audio stream during the initial study of the repo. I do agree with you AKS is at PaaS service but the underlying node on which the bot will be deployed is a VM instance which is IaaS.
Moreover, the endpoint registration here means the endpoint we mentioned while creating the azure bot and giving MS teams access, Since it's the endpoint the bot will finally listen to join a call. It changes during deployment because we get cluster IP / Public IP while on local setup it works through ngrok.
Also to add these steps for deployment are mentioned in the official sample repo ref:https://github.com/microsoftgraph/microsoft-graph-comms-samples/tree/master/Samples/V1.0Samples/AksSamples/teams-recording-bot
so I believe these steps and setup are supported.
The error we are facing is of secrets not mounting if we leave the teams recording bot code apart for a second, I guess the certs should get mounted in the windows node pool as it is not the problem with code but deployment configurations. Maybe we are missing some configurations which are different from the Linux node pool.
Once Again thanks for helping.
No worries for the delay.
Let me bring back one of your statements...
I have read through this requirements doc of the media bot to get an audio stream during the initial study of the repo. I do agree with you AKS is at PaaS service but the underlying node on which the bot will be deployed is a VM instance which is IaaS.
I just wanted to remind here that the master node is a managed instance which is handled by Azure.
Cheers,
I second that
Hi,
Just wanted to shared this detail as last comment for this. See below:
Thanks for the reply.
So this means the VM machine that we are deploying doesn't support persistence volums
Thank you for your quick response.
Yeap that the whole problem and I had to read a lot as well to get to this answer : )
I hope that my assistance was useful for you buddy.
Have a good one.
Best Regards,
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.
I know that it required thorough searching and I am sure it was time-consuming.
I really appreciate your efforts and you deserve the praise for going out of your way to help me.
Thanks a lot.
Btw the repo admin replied to the issue that I created on the official GitHub repo. I am going through that:
ref:
https://github.com/microsoftgraph/microsoft-graph-comms-samples/issues/570
Thanks a lot for your comment buddy and it was a pleasure.
Nice that you got response on GitHub.
Cheers : )
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(19.2, 15%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHB%3C/text%3E%3C/svg%3E)
It sounds like the path indicated in following section of deployment.yaml should be changed as a valid path like /host_mnt/c/certs
volumeMounts:
- mountPath: "C:/certs/"
name: certificate
readOnly: true
tried that also since it's windows nodepool so the path should be C:\certs\ tried that also still got same error.
It sounds like the path indicated in following section of deployment.yaml should be changed as a valid path like /host_mnt/c/certs
volumeMounts:
- mountPath: "C:/certs/"
name: certificate
readOnly: true
!!!!!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(249.60000000000002, 72%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
@Nikheel Jain Recall.ai has hosted recording bot infrastructure.
@Nikheel Jain Have you looked at Recall.ai? They provide a hosted solution for the Microsoft Teams bot so you don't need to build, deploy, and maintain the bots yourself.