Independently Deployed Console
Last updated: 2024-01-20 17:08:53
Independently Deployed Console
Last updated: 2024-01-20 17:08:53
This document describes how to open up CLS's log search and query, monitoring alarm, and dashboard capabilities to others in an independently deployed console. This is a quick and easy way to eliminate the development workload and costs for managing multiple CAM accounts.
Independently Deployed Console
The independently deployed console doesn't require development or logging in to a Tencent Cloud account to use CLS. It has weak permission management and security capabilities and provides only simple password authentication though. We recommend you use it in the private network.
Usage | Supported Features | Free from Tencent Cloud Account Login | Development Workload | Account Permission Management | Login State Conflict |
All CLS features | No | None | Tencent Cloud CAM | None | |
Iframe-embedded console - general embedding | All CLS features | Yes, with iframe embedded into the enterprise Ops system for login through the authentication system | Light, where frontend iframe embedding is required | Enterprise authentication system | Yes |
Iframe-embedded console - SDK embedding | CLS features of log search and analysis and dashboard view | Yes, with iframe embedded into the enterprise Ops system for login through the authentication system | Heavy, where frontend iframe embedding and backend access layer forwarding are required | Enterprise authentication system | No |
All CLS features | Yes, with independent deployment and password-based or password-free login | None | None or password authentication | Yes | |
Grafana's dashboard features excluding alarming | Yes, with Grafana for data access | None | Grafana's permission management system | No |
Using the Independently Deployed Console
CLS provides the image of the independently deployed console in TKE's public image repository, which can be pulled from the TKE console for use.
Prerequisites
The following takes image deployment in a TKE general cluster as an example, which requires an available cluster. If there are no clusters, create one as instructed in Creating a Cluster or create a container instance as instructed in Creating a Container Instance for direct deployment.
Directions
1. Log in to the TKE console and click the name/ID of an available cluster in the cluster list to enter the cluster management page.
2. On the left sidebar, select Workload > Deployment and click Create.
3. On the deployment creation page, configure the following items and use the default values for others.
Image: Click Select Image > Public Image and search for and select the "cls_iframe" image.
Image Tag: Select Latest image tag.
Environment variable:
Environment Variable | Description |
SecretId | |
SecretKey | |
RoleArn | AssumeRole API request parameter. To get the role resource description, go to the CAM console and click the role name. We recommend you use CLS's read-only role.If there is no such role, create one with CLS's read-only access permission for the Tencent Cloud root account as instructed in Creating Role. |
password | Enter the password to access the console with the configured identity. |
Port Mapping: Set Target Port and Port to 3000.
Note:
In the example, LoadBalancer (public network) is selected. We recommend you select LoadBalancer (private network), which is more secure in actual business operations.
4. Click Create Workload to complete the process.
5. Click Services and Routes to view the LB access address bound to the workload.
6. Copy the LB IP address, add port 3000, and enter the password in the browser to access the deployed CLS console.
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No
Feedback