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
DocumentaçãoTencent Kubernetes EngineUse CasesClusterUsing Private DNS to Implement Automatic Domain Name Resolution When Accessing Cluster via Private Network

Using Private DNS to Implement Automatic Domain Name Resolution When Accessing Cluster via Private Network

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2024-12-13 15:57:58

Overview

After private network access is enabled for the current cluster, TKE will access the cluster through the domain name by default. You need to configure Host on the access server to perform DNS queries on the private network. If no DNS rules (Host) are configured, an error "no such host" will be reported when you access the cluster on the access server (by running kubectl get nodes) as shown below:


In practice, configuring Host will increase your management labor costs. Therefore, we recommend you use Tencent Cloud's newly launched Private DNS service, which helps you get things done in just three steps.

Billing description

Private DNS is billed on a pay-as-you-go basis, where the number of private domains and that of DNS requests are billed on a natural day basis. For more information, see Billing Overview.

Available regions

Currently, Private DNS is not available in all the available regions of TKE. For the list of its available regions, see Use Limits.
To access clusters over the private network in regions not covered by Private DNS, you need to manually configure the Host. To use Private DNS in those regions, submit a ticket for application.

Prerequisites

A container cluster has been created and private network access has been enabled. For details, see Creating a Cluster.

Directions

Activating Private DNS

Creating private domain

1. Log in to the Private DNS console.
2. Click Create Private Domain and configure the following options (just use the default values for other parameters). For more information, see Creating Private Domain.


Domain: Enter tencent-cloud.com (domain name allocated by TKE for accessing the cluster).
Associated VPC: Select the node VPC that needs to access the cluster.
3. Click OK.

Configuring DNS records

1. Click the private domain name created above to enter the DNS Records page.
2. Click Add Records and configure the following options:


Host Record: Enter the secondary domain name for accessing the TKE cluster, for example, cls-{{clsid}}.css.
Record Type: Enter A.
Record Value: Enter the private IP for accessing the TKE cluster.
Note:
You can get the Host Record and Record Value from Cluster Management > Cluster > Basic Info. Here, Host Record is the domain name in Access Address, and Record Value is the IP address in Private Network Access, as shown below:



3. Click Save in the Operation column on the right.

Verifying effect

1. Run the following command to access the cluster again.
kubectl get nodes
2. When the following result is displayed, the cluster has been successfully accessed, and the node list has been pulled.



Ajuda e Suporte

Esta página foi útil?

comentários