Help Center/ Migration Center/ Best Practices/ Collecting Details of Azure Azure Kubernetes Service (AKS) Resources
Updated on 2024-12-03 GMT+08:00
View PDF
Share

Collecting Details of Azure Azure Kubernetes Service (AKS) Resources

Before migrating Azure Kubernetes Service (AKS) resources, use MgC to collect resource details, which are necessary for subsequent migration. This section describes the basic principles, preparations, account permission requirements, and specific operations for using MgC to collect AKS resource details efficiently and accurately.

Collection Principles

Figure 1 illustrates how to use MgC to collect AKS resource details.
Figure 1 Principle for collecting AKS resource details
  1. MgC invokes AKS APIs through the Azure SDK to obtain information about resources such as containers and VMs.
  2. MgC receives API call responses, which typically contain extensive resource data.
  3. MgC parses the returned data and extracts key information, such as the number of nodes and number of VM cores. Then, the key information is saved to the database for subsequent analysis and migration.

Preparations

  • Preparing a Huawei account

    Before using MgC, you need to prepare a HUAWEI ID or an IAM user that can access MgC. For details about how to register a HUAWEI ID and create an IAM user, see Preparations.

  • Creating a migration project

    Create a migration project (a simple project is recommended) on the MgC console. For details, see Managing Migration Projects.

  • Preparing Azure credentials

    Obtain the password of the application client that owns the AKS resources, subscription ID used to purchase the AKS resources, tenant ID of the application, and client (application) ID. To learn how to obtain Azure credentials, see How Do I Obtain Azure Credentials?

  • Providing the source credentials

    Add the Azure authentication information to the MgC console as the collection credential. For details, see Managing Credentials.

Required Permissions

Ensure that the application to which the added Azure credentials belong has the following permissions in the resource group and subscription for purchasing the AKS resources:

  • Microsoft.ClassicCompute/virtualMachines/read
  • Microsoft.Insights/MetricDefinitions/Read
  • Microsoft.Management/getEntities/action

For details, see How Do I Configure the Permissions Required for Collecting Details of Azure Containers?

Procedure

Create a discovery task on the MgC console. For details, see Discovering Resources over the Internet.