Open dtzar opened 1 year ago
For this, do you imagine that for an individual application all resources would be represented via K8s manifests or are there instances where you might mix and match Bicep/TF with K8s manifests? Interesting in the split, if that's a viable use case.
@markweitzel @chuxel for input here too
Target primary use case is everything represented in ASO and/or CAPZ. I have not heard of a customer desiring a mixed-use case of ASO/CAPZ plus something else (Bicep/Terraform). The only time I see it is if there is a need to temporarily fill a gap in ASO.
In a modern GitOps workflow for IaC, using Kubernetes as a control plane is an excellent way to accomplish this via Cluster Api Provider for Azure (for self-managed Kubernetes or AKS) and Azure Service Operator (for almost any Azure resource). I'd like this to work with azd tooling.