Separate AgentPool from AKSCluster

[vaspahomov]

What problem are you facing?

AKSCluster not configurable in AgentPool:

• You can not create auto scaling AgentPool
• You can not create multiple AgentPool for AKS cluster
• You can not chose other mode for AgentPool
• AKSCluter not supporting update reconciliation

Before this feature need AgentPool resource: #262

How could Crossplane help solve your problem?

I suggest separate AgentPool from AKSCluster resource:
Remove nodeCount, nodeVMSize fields from spec. And add required systemAgentPoolRef in spec.
In this way:

• it'll be easier to support AgentPool scaling reconciliation
• more readable specs when AgentPool will have more spec parameters

[muvaf]

@vaspahomov Thanks! Yeah, separating the two would be in line with our high fidelity goal for the CRDs.