# Upgrading
Follow the steps to upgrade your product.
1. [Before you begin](#before_begin)
2. [Preparing for upgrading](#dependency)
2. [Upgrading](#upgrading)
3. [Verifying upgrading](#verify)
4. [Post-upgrading steps](#post-upgrading)
## 1. Before you begin
{: #before_begin}
### Checking supported upgrading paths
{: #supported_path}
<!--- Not all the upgrading paths are supported. When users read this page, the first concern is which version they can upgrade to, and whether there are any limitations for their environments.
Add all the supported upgrading paths in this section. See the following examples:
For product xx,it can only be upgraded to version 3.5 from version 3.0.1.
---->
### Limitations
{: #limitation}
<!---
Before users upgrade to a specific version, they need to be notified of the new known issues. For example:
- Product 2.11 is not available for Linux , for which the latest supported version is 2.10.
- All metrics that were stored in version 2.0 will be lost after upgrading to version 2.1.
---->
## 2. Preparing for upgrading
{: #preparation}
### Checking system requirements
<!---
Inform users to meet the new system requirements. Especially we need to point out those changed requirements between the old version and the new version for users' convenience. For example, Storage requirements.
Format details:
|Storage provider|Storage type|Storage class|Storage access mode|Recommended reclaim policy| Encryption supported on the supported storage class|Minimum amount of storage|Minimum amount of memory|I/O requirements|Network requirements|
- Hardware requirements
Format example:
|Node role|Hardware|Number of servers|Minimum available vCPU|Minimum memory|
|--|--|--|--|--|
- Security requirements
- Command-line tools requirements
--->
### Getting an account with enough privilege for upgrading
{: #getting_role}
<!---
Not all the roles can be used to upgrade a product. Users need to prepare a privileged role, such as an Administrator role. List the role that can be used to upgrade your product here.
For example:
Ensure that you use the Administrator role to upgrade your product xx.
---->
### Performing a backup
{: #supported_path}
<!---
Backup is needed for disaster recovery after a upgrade. Inform users to complete a backup before they begin the upgrade.
--->
### Other dependencies
<!---
Inform users to set up the dependencies before they upgrade your product. See the following examples:
- Before you upgrade product xx, you need to get access to the new container images.
--->
## 3. Upgrading
{: #upgrading}
<!---
Do not stack all the steps here, such as the preparation steps, but add only the steps about upgrading a specific product here.
--->
### Upgrading by using the console
### Upgrading by using the CLI
## 4. Verifying upgrading
{: #verify}
<!---
Add the guide about how to check whether the upgrade is successful in this section.
--->
## 5. Post-upgrading steps
{: #post-upgrading}
<!---
After upgrading your product, you might need to do some additional steps. List such steps here.
For example:
After product xx is upgraded, you need to migrate automation data.
After product xx is upgraded, you need to upgrade capabilities and runtimes.
--->
