tencent cloud

Tencent Kubernetes Engine

Release Notes and Announcements
Release Notes
Announcements
Release Notes
Product Introduction
Overview
Strengths
Architecture
Scenarios
Features
Concepts
Native Kubernetes Terms
Common High-Risk Operations
Regions and Availability Zones
Service Regions and Service Providers
Open Source Components
Purchase Guide
Purchase Instructions
Purchase a TKE General Cluster
Purchasing Native Nodes
Purchasing a Super Node
Getting Started
Beginner’s Guide
Quickly Creating a Standard Cluster
Examples
Container Application Deployment Check List
Cluster Configuration
General Cluster Overview
Cluster Management
Network Management
Storage Management
Node Management
GPU Resource Management
Remote Terminals
Application Configuration
Workload Management
Service and Configuration Management
Component and Application Management
Auto Scaling
Container Login Methods
Observability Configuration
Ops Observability
Cost Insights and Optimization
Scheduler Configuration
Scheduling Component Overview
Resource Utilization Optimization Scheduling
Business Priority Assurance Scheduling
QoS Awareness Scheduling
Security and Stability
TKE Security Group Settings
Identity Authentication and Authorization
Application Security
Multi-cluster Management
Planned Upgrade
Backup Center
Cloud Native Service Guide
Cloud Service for etcd
TMP
TKE Serverless Cluster Guide
TKE Registered Cluster Guide
Use Cases
Cluster
Serverless Cluster
Scheduling
Security
Service Deployment
Network
Release
Logs
Monitoring
OPS
Terraform
DevOps
Auto Scaling
Containerization
Microservice
Cost Management
Hybrid Cloud
AI
Troubleshooting
Disk Full
High Workload
Memory Fragmentation
Cluster DNS Troubleshooting
Cluster kube-proxy Troubleshooting
Cluster API Server Inaccessibility Troubleshooting
Service and Ingress Inaccessibility Troubleshooting
Common Service & Ingress Errors and Solutions
Engel Ingres appears in Connechtin Reverside
CLB Ingress Creation Error
Troubleshooting for Pod Network Inaccessibility
Pod Status Exception and Handling
Authorizing Tencent Cloud OPS Team for Troubleshooting
CLB Loopback
API Documentation
History
Introduction
API Category
Making API Requests
Elastic Cluster APIs
Resource Reserved Coupon APIs
Cluster APIs
Third-party Node APIs
Relevant APIs for Addon
Network APIs
Node APIs
Node Pool APIs
TKE Edge Cluster APIs
Cloud Native Monitoring APIs
Scaling group APIs
Super Node APIs
Other APIs
Data Types
Error Codes
TKE API 2022-05-01
FAQs
TKE General Cluster
TKE Serverless Cluster
About OPS
Hidden Danger Handling
About Services
Image Repositories
About Remote Terminals
Event FAQs
Resource Management
Service Agreement
TKE Service Level Agreement
TKE Serverless Service Level Agreement
Contact Us
Glossary

Native Node Login Methods

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-06-24 16:34:38

Overview

This document describes the two methods of login to native nodes, namely, SSH key login and one-click login via OrcaTerm.

Method 1: SSH Key Login

For node pools

Assign an SSH key when creating a node pool
Modify the SSH key associated with an existing node pool
You can assign an SSH key to a node pool during the creation of the node pool. After a scale-out of the node pool, the SSH key is automatically assigned to the new nodes.
1. Log in to the TKE console and select Cluster in the left sidebar.
2. On the cluster list page, click the ID of the target cluster to go to the details page.
3. Select Node Management in the left sidebar, click Create and select Native Node on the Node Pool page.
4. On the Create node pool page, select SSH Key.
5. Click Create node pool.
Go to the details page of the node pool and modify the associated SSH key in the launch configuration section. The new SSH key takes effect only for new nodes in the node pool and does not affect the existing native nodes.
1. Log in to the TKE console and select Cluster in the left sidebar.
2. On the cluster list page, click the ID of the target cluster to go to the details page.
3. Select Node Management in the left menu bar, and click the Node Pool ID on the Node Pool page to enter the node pool details Page.
4. On the details page of the node pool, click

next to Associate SSH key in the launch configuration section.
5. On the Set node pool SSH key page, select an SSH key.
6. Click OK.

For nodes

Enable or modify SSH key login for a node
Enable or modify node login for multiple nodes at a time
If no SSH key is assigned to a node pool, you can enable and modify SSH key login for a single node in the node pool.
1. Log in to the TKE console and select Cluster in the left sidebar.
2. On the cluster list page, click the ID of the target cluster to go to the details page.
3. Select Node Management in the left menu bar, and click the Node Pool ID on the Node Pool page to enter the node pool details Page.
4. In the node list of the node pool page, select More > Key Management on the right side of the row for the node.
You can assign an SSH key to multiple nodes at a time.
1. Log in to the TKE console and select Cluster in the left sidebar.
2. On the cluster list page, click the ID of the target cluster to go to the details page.
3. Select Node Management in the left menu bar, click the Node Pool ID on the Node Pool page to enter the node pool details Page.
4. On the details page of the node pool, select multiple nodes as needed and choose More > Batch set SSH key.
Note:
1. Modifying the SSH key assigned to a node does not require the node to restart.
2. When you enable or modify node login for the first time or modify an SSH key that has been assigned to a node, the operation takes one to two minutes.
3. We recommend that the number of nodes for which you enable or modify SSH key login at a time do not exceed 20.
4. Batch enabling or modification of node login does not override the SSH keys that have been assigned to nodes.

Method 2: One-Click Login via OrcaTerm

1. Log in to the TKE console, and select Cluster in the left sidebar.
2. On the cluster list page, click the cluster ID to enter the cluster details page.
3. Select Node Management in the left menu bar, and click the Node Pool ID on the Node Pool page to enter the node pool details Page.
4. On the node pool details page, ensure that Tencent Cloud Automation Tools under Ops information is in the enabled status.
5. In the node list page of the node pool page, select More > Log in on the right side of the row for the node.


Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan