- Release Notes and Announcements
- [January 15, 2024]Announcement on the Official Launch of CCN Routing Reception and Routing Propagation Policies
- [July 3, 2023] Start Charging on CCN Connected Network Instances and Inbound Traffic
- Jul. 26, 2022 - CCN Tagging Upgrade
- Feb 10, 2022 - CCN API Authentication Upgrade
- Jun. 25, 2021 - Free Hangzhou-Shanghai and Hangzhou-Nanjing Lines
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Best Practices
- API Documentation
- FAQs
- Troubleshooting
- Service Agreement
- Contact Us
- Release Notes and Announcements
- [January 15, 2024]Announcement on the Official Launch of CCN Routing Reception and Routing Propagation Policies
- [July 3, 2023] Start Charging on CCN Connected Network Instances and Inbound Traffic
- Jul. 26, 2022 - CCN Tagging Upgrade
- Feb 10, 2022 - CCN API Authentication Upgrade
- Jun. 25, 2021 - Free Hangzhou-Shanghai and Hangzhou-Nanjing Lines
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Best Practices
- API Documentation
- FAQs
- Troubleshooting
- Service Agreement
- Contact Us
Tencent Cloud will undergo an upgrade of the CCN tagging feature on July 26, 2022 from 0:00-2:00 (UTC+8). The upgrade information is as follows:
Removing the Regional Attribute from the CCN Tags
For now, CCN tags have the regional attributes. For example, you tag the instance CCN A in Guangzhou region with "test1:A", and tag it in Shanghai region with "test2:B". When you query tags of CCN - A, "test1:A" is returned for Guangzhou region, and "test2:B" is returned for Shanghai region.
However CCN service does not have any regional restrictions and differences. Adding the regional attributes brings in unnecessary. After the upgrade, the regional attributes of the CCN tags are removed, which means you do not need to specify the region ID for adding and querying tags. For example, after the upgrade, when you query tags of CCN - A, both "test1:A" and "test2:B" are returned.
After the upgrading, all existing tags of CCN instances are updated to tags without regional attributes.
CCN instance | Before upgrade (with regional attribute) | After upgrade (without regional attribute) |
CCN - A | Guangzhou: test1:A
Shanghai: test2:B | test1:A, test2:B |
Upgrade Impact
During the upgrade, CCN data transmission and API calls are not affected.
During the upgrade, both the tags with/without regional attributes are returned for tag queries.
After the upgrade, the regional attribute will be removed from all existing tags. Newly created tags do not include the regional attribute. Please note this upgrade in advance to avoid business impact.
Upgrade Sample:
1. Before the upgrade: The CCN tags have the regional attribute. For example, in the Guangzhou region, tag the following CCN with test1:A.
2. During the upgrade: Both the tags with/without regional attributes are returned for tag queries. But the CCN data transmission and API calls are not affected.
3. After the upgrade: The regional attribute will be removed from all existing CCN tags. For example, the CCN tag "test1: A" is region-insensitive.
Yes
No
Was this page helpful?