Cloud Load Balancer
- Release Notes and Announcements
- Product Introduction
- Product Comparison
- Purchase Guide
- CLB Resource Package
- Getting Started
- Operation Guide
- CLB Instance
- CLB Listener
- Real Server
- Health Check
- Certificate Management
- Log Management
- Monitoring and Alarm
- Cloud Access Management
- Practical Tutorial
- Obtaining Real Client IPs
- Ops Guide
- Troubleshooting
- API Documentation
- Instance APIs
- Listener APIs
- Backend Service APIs
- Target Group APIs
- Redirection APIs
- Other APIs
- Classic CLB APIs
- Making API Requests
- Load Balancing APIs
- CLB API 2017
- Making API Requests
- Request Structure
- Returned Results
- General APIs
- Classic CLB APIs
- APIs for CLB Instances
- APIs for Listeners
- CLB Real Server APIs
- APIs for Health Check
- FAQs
- Troubleshooting Health Check Issues
DocumentationCloud Load BalancerRelease Notes and Announcements [March 6, 2023] Launching Domain Name-Based Public CLBs
[March 6, 2023] Launching Domain Name-Based Public CLBs
Last updated: 2024-01-04 09:44:16
[March 6, 2023] Launching Domain Name-Based Public CLBs
Last updated: 2024-01-04 09:44:16
Dear Tencent Cloud user,
For a better service, we are going to upgrade the architecture of Tencent Cloud Load Balancer (CLB) starting from March 6, 2023 at 00:00:00 (UTC+8). After the upgrade, the public network CLB service will be delivered through domain names, and VIPs may change dynamically with business requests and will no longer be displayed in the console.
For CLB users registered after the upgrade, the upgraded CLB service is used by default. For more information, see Getting Started with Domain Name-Based CLB.
Existing users registered before the upgrade can choose to use the original CLB service, or try the upgraded CLB service by applying for beta test or upgrading existing instances.
CLB Service Comparison Before and After the Upgrade
Item | After Upgrade | Before Upgrade |
SLA | 99.99% | 99.95% |
Domain names supported | Yes | No |
Automatic VIP scaling supported | Yes | No |
VIP changes | VIPs may change dynamically with business requests and will no longer be displayed in the console. | VIPs are fixed. |
Health check source IP | 100.64.0.0/10 IP range by default, helping prevent IP conflicts | CLB instance VIP by default, which can be switched to the 100.64.0.0/10 IP range |
Directions for Trying the Upgraded CLB Service
Note:
These directions are intended for existing users registered before the upgrade. For new CLB users registered after the upgrade, the upgraded CLB service is used by default.
Method 1: Apply for beta test and purchase upgraded instances based on your use scenarios.
Optional upgrade to domain name-based CLB to apply for beta test in transition mode. After the application is approved, create a CLB instance and choose the dynamic IP mode. The created instance provides the upgraded CLB service.
Complete upgrade to domain name-based CLB to apply for beta test in one-click update mode. After the application is approved, CLB instances created provide the upgraded CLB service by default.
Note:
In the beta test, you can no longer create a CLB instance with a fixed IP address.
Method 2: Upgrade your existing CLB instances. For more information, see Directions for Upgrading to Domain Name-Based CLB.
Preparations
1. Configure your business service to be accessible through CNAME resolution.
2. Change the health check source IP to the 100.64.0.0/10 IP range. For more information, see Changing Health Check Source IP.
Impact
The upgrade does not affect the forwarding service of CLB or change the usage fee.
After the upgrade, CLB implements automatic VIP scaling based on business requests. VIPs change dynamically and will no longer be displayed in the console.
After the upgrade, the health check source IP of CLB uses the 100.64.0.0/10 IP range by default. For more information, see Changing Health Check Source IP.
After the upgrade, rollback is not supported.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No