Dedicated RG for ACR to support alternate lifecycle

[sassoftware]

Dedicated RG for ACR to support alternate lifecycle

[NormJohnIV]

I disagree. The document talks about a user wanting to test out many ways to use the container registry an thus put it in it own rg. We are not doing that. We can already use the existing ACR setup for multiple viya deployments on the same cluster or in clusters existing in the same rg. Furthermore, with our IaC code this seems like an anti pattern. Who would control the ACR since only one deployment would have it? What happens it they want to take down that infrastructure but others are using the acr? If users want to have cross rg ACR I think that should be done outside of this tooling and they just tell viya about it. That is already supported.

[thpang]

Does this need more discussion @manoatsas ? If a meeting is needed set one up. If @NormJohnIV response was sufficient, please close. Thx.

[manoatsas]

I'd keep the discussion here for input from the field where more realistic use cases would arise. Primary use case is not necessarily shared ACR but to account for lifecycle differences between AKS and ACR. ACR may be once per release of Viya4 whereas AKS and other components would have shorter lifecycles (e.g., weekends, nightly or other cycles) to reduce cloud costs.