Deploy a .NET application on Microsoft Azure Cobalt 100 VMs

Give feedback

How would you rate this Learning Path?

Review frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
Which Azure Cobalt 100 VM series should I use for the self-hosted runner?
Azure Cobalt 100 offers general-purpose Dpsv6/Dplsv6 and memory-optimized Epsv6 series. Choose based on your build and deployment needs. The Learning Path doesn’t prescribe a specific size.
Do I have to use a self-hosted runner, or can I use GitHub-hosted `arm64` runners?
GitHub-hosted arm64 runners are generally available for Team and Enterprise Cloud accounts. If your account qualifies, you can use hosted arm64 runners instead of a self-hosted runner.
How do I know the self-hosted GitHub Actions runner is ready before triggering the workflow?
Confirm the runner is installed on the Azure Cobalt 100 VM and appears online in GitHub. Don’t start the workflow until the runner reports an available status.
What result should I expect after applying the Terraform configuration?
Terraform creates an AKS cluster with node pools based on Azure Cobalt 100. This cluster is then targeted by the GitHub Actions workflow that deploys the .NET application.
How can I verify the .NET application is running on Arm-based nodes in AKS?
Check that the deployed workload is scheduled onto the AKS node pool created for Azure Cobalt 100. Seeing pods running on that pool indicates the application is using arm64 nodes as intended.

Share

Tell others about this Learning Path.

Back
Return to Servers and Cloud Computing