Roadmap for ASO vs Crossplane

[artisticcheese]

Hello,

We are pretty big company heavily relying on Azure for all our infra. We are heavy user of IaaC (terraform) and seriously looking in having IaaC done via K8s for some resource types and hence choice came to ASO vs Crossplane.
We tried both (in fact started with ASO and did not even consider Crossplane).
Within less then a week run into issue in limited amount of resource types supported by ASO. Specifically APIM missing most important resource type APIOperation (#3813)
Switched to Crossplane where more resource types are supported but run into another issue there - specifically very little activity on Azure provider and very little support for issues raised.
So we are on crossroads at this point where to go. We really like ASO (vs Crossplane) due to higher activity, somewhat better support and sponsorship from Microsoft down the road and having single vendor is big intererest for us.
Any suggestions whether we shall continue waiting for necessary resource types to be added and stick ASO (it's been almost a year since request was open to add that resource type) or try work issues out with crossplane (where there is seems to be even less activity then in ASO but better resource type support)

[theunrepentantgeek]

We (the maintainers of ASO) are a part of the Azure Kubernetes product group, and we're not going anywhere - we're actively managing the ASO project and continuing to grow the list of supported resources. We aim for a new release of ASO about every two months. This is an actively supported project.

There's a large list of requested resources - and, regrettably, only a limited amount of time.

I've tagged #3813 for re-triage in mid-January (when everyone is back from end-of-year leave) and tentatively put it into the v2.13 milestone for consideration.

If you are so inclined, we do accept contributions - all the APIM resources are external contributions that we helped get across the line. We have extensive documentation for contributors - and we prioritize working with folks to get their PRs merged, regardless of other prioritization work.