Feature: Support resources needed by CAPZ

[matthchr]

The list of resources we are currently lacking for CAPZ is:

• VM extensions (Feature: Add support for VM and VMSS extensions #2891)
• VMSS extensions (Feature: Add support for VM and VMSS extensions #2891)
• Azure Bastions (Feature: Add support for Azure Bastions #2892)
• NAT Gateways (Feature: Support NAT Gateways #2893)
• Inbound NAT rules (Feature: Support LoadBalancer InboundNATRules #2894)
• Availability Sets (Feature: Add support for Microsoft.Compute/availabilitySets #1930)
• Private DNS (private zones, vnetlinks, and recordsets) (Add PrivateDNSZone resource #2086 is a PR for this but not merged yet).
• RouteTable (Feature: Support RouteTable and Route #2284)
• Virtual Network Peerings

The full list of in-use services can be found here: https://github.com/kubernetes-sigs/cluster-api-provider-azure/tree/master/azure/services

[matthchr]

I just realized that we already support Peerings. Updated the list to reflect that

[nojnhuh]

Resource health also falls into this category: #2762

CAPZ also uses privatdns.VirtualNetworkLinks and privatedns.RecordSets and I can't quite tell if those are supported in ASO? I see PrivateDnsZonesVirtualNetworkLink and the record types listed here: https://azure.github.io/azure-service-operator/reference/. But there's no sample YAML and I don't see them listed anywhere on this page: https://azure.github.io/azure-service-operator/reference/network/v1beta20180901/.

Otherwise I took another look through the list and everything looks up to date 👍

[matthchr]

Yes we support RecordSets and VirtualNetworkLinks. IIRC both of these were added for the upcoming v2.0.0 release and they aren't on the full website yet because that release hasn't gone out yet, but they will be there shortly.

[dtzar]

@matthchr - can you please reflect the latest status with the checklist of items at the top of this description? I can see it hasn't been updated since April 2022.

[mboersma]

Assuming this list represents ASO services currently implemented, I don't see any delta with CAPZ services: https://github.com/kubernetes-sigs/cluster-api-provider-azure/tree/main/azure/services.

@mattchr are there still gaps here?

[matthchr]

Yes there are definitely some gaps here.

ASO has a list of supported resources here: https://azure.github.io/azure-service-operator/reference/

I believe the checklist above is correct. We do not currently have support for:

• VM extensions (Feature: Add support for VM and VMSS extensions #2891)
• VMSS extensions (Feature: Add support for VM and VMSS extensions #2891)
• Azure Bastions (Feature: Add support for Azure Bastions #2892)
• NAT Gateways (Feature: Support NAT Gateways #2893)
• Inbound NAT rules (Feature: Support LoadBalancer InboundNATRules #2894)
• Availability Sets (Feature: Add support for Microsoft.Compute/availabilitySets #1930)
• VirutalMachineImages (not 100% sure what this is actually?)
• ScaleSetVMs (I think from looking at CAPZ code this is related to VMSS Flex, since with uniform you dont provision VMs you just edit the parent VMSS?)

The rest of the resources CAPZ uses I believe we have support for already.

[mboersma]

I believe the checklist above is correct.

Excellent, thank you for the confirmation @matthchr! I'll use this list to try to fill in the gaps for CAPZ with SDK v2 until these resources are implemented in ASO.

[matthchr]

Rather than tracking this as a block, I've broken out individual items for the above. I edited them in to my post above and the original issue.

I'll close this in favor of those once we get clarity on what these two things actually are:

• VirutalMachineImages (not 100% sure what this is actually?)
• ScaleSetVMs (I think from looking at CAPZ code this is related to VMSS Flex, since with uniform you dont provision VMs you just edit the parent VMSS?)

Which ARM resources do these refer to?

[matthchr]

I've added a CAPZ label for now to track this work too: capz Required for CAPZ ASO adoption

[matthchr]

Ah, VirtualMachineImages is just LIST for CAPZ: https://github.com/kubernetes-sigs/cluster-api-provider-azure/blob/main/azure/services/virtualmachineimages/client.go

[matthchr]

and here's ScaleSet VMs issue: #2895

It's also not a real resource but it seems a reasonable ask for there to be a way to manage individual VMs through the ASO API.

[matthchr]

I'm closing this in favor of all of the linked issues above that can track things at a more granular level. Use the capz Required for CAPZ ASO adoption label for an aggregate view of what more needs to be done.