I would like to deploy multiple Teams-recording-bot on one VM with different namespaces.

Expected behavior
https://github.com/microsoftgraph/microsoft-graph-comms-samples/tree/master/Samples/V1.0Samples/AksSamples/teams-recording-bot
I would like to deploy multiple sample bots above on one VM with different namespaces.
The procedure that was executed is as follows.

Execution procedure
First, the first bot was deployed by following the steps from "1. Setup" to "3. Deploy bot to AKS".
https://github.com/microsoftgraph/microsoft-graph-comms-samples/blob/master/Samples/V1.0Samples/AksSamples/teams-recording-bot/docs/deploy/aks.md

Next, create a new namespace and secret with "Deploy bot to AKS".
When I tried to deploy the second bot, I got the following error:

"Error: rendered manifests contain a resource that already exists. Unable to continue with install: ConfigMap" teams-recording-bot-tcp-services "in namespace" ingress-nginx "exists and cannot be imported into the current release: invalid ownership metadata annotation validation error: key "meta.helm.sh/release-namespace" must equal "teams-recording-bot2": current value is "teams-recording-bot" "

I thought that the cause was that the ConfigMap was duplicated, so I created a different ConfigMap by doing the following.

• Changed the value of "name:" on the second line of "Chart.yaml" to "teams-recording-bot2"

After that, when I tried to deploy, the following error occurred.

"Error: rendered manifests contain a resource that already exists. Unable to continue with install: Service" nginx-ingress-ingress-nginx-controller "in namespace" ingress-nginx "exists and can not be imported into the current release: invalid ownership metadata; annotation validation error: key "meta helm.sh / release-name" must equal "teams-recording-bot2": current value is "teams-recording-bot"; annotation validation error: key "meta.helm.sh / release-namespace "must equal" teams-recording-bot2 ": current value is" teams-recording-bot ""

We thought that this error could be solved by creating another nginx-ingress-ingress-nginx-controller and using it, and implemented the following.

• Changed the value of "name:" on the 5th line of "external.yaml" to "nginx-ingress-ingress-nginx-controller2"

After that, the second bot was successfully deployed and the bot started.

Describe the issue
There is a problem that the Teams meeting cannot be started for the second deployed bot.

Question matters
In this procedure, it was assumed that the purpose could be achieved by configuring as shown in the figure below.
(Attach "Assumed configuration.png")

• Is the structure of this figure correct?
• Is there any excess or deficiency in this procedure?

Start with docs/deploy/aks.md and inspect the Helm resources referenced by Chart.yaml and external.yaml, especially the ConfigMap and ingress controller names and namespaces. Compare the first and second deployment procedures and verify whether both bots can start Teams meetings; done means the supported multi-bot configuration and any required documentation are clear.