microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

Issue with Deploying Teams Recording Bot

Open
#570 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
253
Forks
275
Avg merge
1d 5h
Merged PRs (30d)
1

Description

Describe the issue
on deployment team-recording bot namespace tls-ingress is not in ready state. So the certificate is note ready

deployment code:
https://github.com/jinik21/TeamsRecordingBot/blob/master/03_IaC/00_AzureCLI/02_AKS_iac.ps1

Expected behavior
certificate should be generated and teams recording bot container should be ready.
Logs
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

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with 03_IaC/00_AzureCLI/02_AKS_iac.ps1 and inspect the AKS resources, certificate, and volume configuration. Reproduce the deployment with kubectl, checking the ingress-tls certificate and pod events; done means the certificate is ready and the teams-recording-bot pod reaches Ready without FailedMount errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, kubernetes, powershell
Domain
cloud, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.