Unable to create 2 AGIC on the same cluster

[mikevo13]

Describe the bug Got below error message when trying to create 2 AGICs in the same cluster targeting 2 Application gateways:

Error: rendered manifests contain a resource that already exists. Unable to continue with install: Secret "networking-appgw-k8s-azure-service-principal" in namespace "kube-addon" exists and cannot be imported into the current release: invalid ownership metadata; annotation validation error: key "meta.helm.sh/release-name" must equal "private-ip": current value is "public-ip"

To Reproduce Initiate 2 Helm deployments with below configurations:

{
	appgw          = {
		name                  = "app-gw-priv-test"
		resourceGroup         = "rg-app-gw-test"
		shared                = "false"
		subResourceNamePrefix = "kube"
		subscriptionId        = "***********"
		usePrivateIP          = "true"
	}
	armAuth        = {
		secretJSON = "****"
		type       = "servicePrincipal"
	}
	kubernetes     = {
		ingressClass = "private-agw-ingress"
	}
	rbac           = {
		enabled = true
	}
	verbosityLevel = 3
}

{
	appgw          = {
		name                  = "app-gw-pub-test"
		resourceGroup         = "rg-app-gw-test"
		shared                = "false"		
		subResourceNamePrefix = "kube"
		subscriptionId        = "***********"
		usePrivateIP          = "false"
	}
	armAuth        = {
		secretJSON = "***"
		type       = "servicePrincipal"
	}
	kubernetes     = {
		ingressClass = "public-agw-ingress"
	}
	rbac           = {
		enabled = true
	}
	verbosityLevel = 3
}

Ingress Controller details

• Output of kubectl describe pod <ingress controller> . The pod name can be obtained by running helm list.
• Output of `kubectl logs .
• Any Azure support tickets associated with this issue.

[ferronsw]

Same issue as I reported only difference I need an upgrade path #1355

[JiayangZhou]

You can achieve two AGIC deployments in the same cluster by using ingressClass as you already did, do you have them in two separate namespaces?

[akshaysngupta]

This is happening as both AGICs are using the same ingress class resource name which will lead to conflict. You can provide a different value for ingress class name by using providing kubernetes.ingressClassResource.name parameter in the Helm values. Remember to use the same name in the Ingress resource as well.