Release Notes and Announcements
- Release Notes
- Announcements
- Release Notes
Product Introduction
Purchase Guide
- Purchase Instructions
- Purchase a TKE General Cluster
- Purchasing Native Nodes
- Purchasing a Super Node
Getting Started
Cluster Configuration
- General Cluster Overview
- Cluster Management
- Network Management
- Storage Management
- Node Management
- Images
- 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
- Control Plane Security
- Application Security
- Cluster Security Enhancement Capability
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
- Cost Management
- Hybrid Cloud
- AI
Troubleshooting
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
- Node Pool APIs
- 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 Standard 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

externalnodeproxy (Internal Service Proxy Component for Registered Node Direct Connect Edition)

Baixar

Modo Foco

Tamanho da Fonte

Última atualização: 2026-10-23 15:37:52

Traduzido por IA

Component Introduction
This component is automatically created when the dedicated line edition capability for registered nodes is enabled for the cluster. It occupies an IP address in the VPC subnet specified when registered nodes are enabled for the user cluster to listen for proxy services. For details, see Registered Node Dedicated Line Edition Description.
Changelog
Release Date
Version Number
Change Content
Limitations and Impacts
2026-03-23
1.0.3
1. Set worker_connections to 4096 in the nginx configuration.
2. Multi-replica deployment improves backend availability.
Note: This will occupy one more IP address in the user VPC subnet than previous versions.
This upgrade will not affect existing services. Components may be unavailable during the upgrade. It is recommended to upgrade during off-peak hours.
2025-12-04
1.0.2
Add a custom HEADER to the nginx configuration to distinguish registered node requests.
This upgrade will not affect existing services. Components may be unavailable during the upgrade. It is recommended to upgrade during off-peak hours.
2024-02-20
1.0.1
Set the number of replicas based on whether the cluster is idle.
This upgrade will not affect existing services. Components may be unavailable during the upgrade. It is recommended to upgrade during off-peak hours.
2023-11-22
1.0.0
The release agent component supports installation as a component.
This upgrade will not affect existing services. Components may be unavailable during the upgrade. It is recommended to upgrade during off-peak hours.

Ajuda e Suporte

Esta página foi útil?

Você também pode entrar em contato com a Equipe de vendas ou Enviar um tíquete em caso de ajuda.

comentários

tencent cloud

Tencent Kubernetes Engine

externalnodeproxy (Internal Service Proxy Component for Registered Node Direct Connect Edition)

Component Introduction

Changelog

Ajuda e Suporte

Release Date	Version Number	Change Content	Limitations and Impacts
2026-03-23	1.0.3	1. Set worker_connections to 4096 in the nginx configuration. 2. Multi-replica deployment improves backend availability. Note: This will occupy one more IP address in the user VPC subnet than previous versions.	This upgrade will not affect existing services. Components may be unavailable during the upgrade. It is recommended to upgrade during off-peak hours.
2025-12-04	1.0.2	Add a custom HEADER to the nginx configuration to distinguish registered node requests.	This upgrade will not affect existing services. Components may be unavailable during the upgrade. It is recommended to upgrade during off-peak hours.
2024-02-20	1.0.1	Set the number of replicas based on whether the cluster is idle.	This upgrade will not affect existing services. Components may be unavailable during the upgrade. It is recommended to upgrade during off-peak hours.
2023-11-22	1.0.0	The release agent component supports installation as a component.	This upgrade will not affect existing services. Components may be unavailable during the upgrade. It is recommended to upgrade during off-peak hours.