This article describes the operational procedures for creating, viewing, and destructing Polaris instances through the Tencent Service Framework (TSF) console, helping you quickly get familiar with TSF console operations.
Operation Steps
Instance Creation
1. Log in to TSF console, in the left sidebar, select Polaris (North Star).
2. On the instance list page, click New.
3. On the new PolarisMesh page, select the relevant configurations based on your business requirements.
Parameter
Description
Billing Modes
Yearly/monthly subscription and pay-as-you-go billing methods are supported. For details about the price, see Polaris Pricing.
Open Source Edition
2.1.1.0-RC2
Product Edition
Enterprise Edition: The Enterprise Edition is suitable for production or test environments. It supports deployment in multiple AZs and possesses all the capabilities of the Service Governance Center: registry + configuration center + governance center.
Basic Edition: The Basic Edition provides the capabilities of a registry and a configuration center. It is suitable for production or test environments. If governance capabilities are required, we recommend purchasing the Enterprise Edition.
Development Edition: The Development Edition supports only a single node with a 1-core 1-GB specification and is recommended for trial use only. It does not have disaster recovery capabilities. To ensure the stability of your business, the Enterprise Edition or Basic Edition is strongly recommended for production environments.
Standard Edition (Sold Out): It is suitable for production environments and provides governance capabilities for registries, configuration centers, and basic services.
Product Specifications
Select the quota for access nodes based on your business requirements. The number of nodes is the number of clients accessing Polaris online, which is the number of application processes accessing the Polaris server. Client types accessing Polaris include polaris sdk, polaris agent, sidecar, polaris controller, and so on.
Deployment Architecture
High availability architecture is supported. Select intra-city multi-AZ or cross-city multi-AZ based on your actual business requirements.
Region Configuration
Intra-city multi-AZ: Based on your actual business architecture plan, select the region closest to where your business is deployed.
Registration, Configuration, and Governance - Polaris automatically deploys instances across multiple AZs.
After the instance is created, you can view the actual deployment architecture. To do this, click the instance ID to go to the Instance Information page, and locate the specific deployment architecture in the Deployment Architecture section at the bottom.
Cross-city multi-AZ: Based on your actual business architecture plan, select multiple regions for instance networking.
The first region is designated as the primary region of the cluster by default. The primary region cannot be deleted.
The primary region and other regions are identical in terms of usage, and both support data read and write operations.
You can configure access node specifications separately for multiple regions.
You can configure the access cluster network separately for multiple regions.
A maximum of 5 regions are supported.
Cluster Network
Plan the cluster network based on your business network. The selected VPC must be the same as the VPC where your business is located. The selected subnet has no consistency restriction.
Monitoring and Logging
Select whether to enable the event center, operation records, and alarm capabilities.
Note:
The PolarisMesh Event Center, operation records, and alarm data are stored in the CLS log service. After you enable this feature, the log set tse_logset and the topics: polarismesh_event, polarismesh_operation, and polarismesh_alarm are automatically created. You can query these events, operation records, and alarm configurations on the PolarisMesh console.
Note that CLS is a separately billed product. For example: 1 million events and operation records incur a fee of approximately CNY 10.29/month. This fee is not included on the purchase page. For detailed billing information, see CLS Billing Overview.
Name
The name can contain up to 60 characters, including uppercase and lowercase letters in Chinese and English, hyphens (-), and underscores (_). Once created, the name cannot be modified.
Resource Tag
Optional. For detailed usage methods, see Tag Management.
4. Click Buy Now. On the status bar of the Polaris list page, you can view the progress of instance creation.
Access Method
Click the instance "ID". On the Instance Information page of the instance details, you can view the instance's access IP address.
Console Access Address
Public network access is enabled by default. You can click the public network address link to access the Polaris console. For public network access, it is recommended to configure access security policies. You can control public network access by setting up an allowlist.
Note:
To ensure the security of your business, please log in to the Polaris console promptly to modify your initial password. The initial login credentials for the Polaris console are as follows:
Initial username: polaris
Initial password: polaris@{random}
Client Access IP Address
The client access address is the address exposed by the Polaris server for user services to connect to Polaris for service communication and configuration. By default, client access is provided via VPC private network access. Public network access can be used for development, debugging, or auxiliary management. For production use, private network access is recommended to avoid potential security risks from public network access. If public network access must be enabled for special needs, configure an allowlist that excludes 0.0.0.0.
For example, for a Java application, using the polaris-java sdk, you can add a polaris.yml file under the current directory of the application's classpath to configure the server IP address information.
global:
serverConnector:
addresses:
- 10.10.0.73:8090
Monitoring Data Reporting IP Address
Configure the monitoring reporting address in the client to upload Polaris monitoring data.
Deleting an Instance
Note:
Once a Polaris instance is terminated, its services become unavailable and all data is permanently destroyed. This operation is irreversible. Exercise extreme caution when performing this action.
