- Release Notes and Announcements
- Release Notes
- Announcements
- [Important] API Gateway Product Sales Discontinuation Announcement
- [August 30, 2024] Discontinuation Notice for Toronto Region
- [March 1, 2024] Security Management Notice for the Use of Default Domain Name in API Gateway
- [August 15, 2022] Billing of Public Network Outbound Traffic from API Gateway to Backend Services
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Instance Management
- Service Management
- Creating API
- API Creation Overview
- Creating APIs Connecting to the Public URL/IP Backend
- Creating APIs Connecting to the VPC Resource Backend
- Creating APIs Connecting to the SCF Backend
- Creating API for Interconnecting Backend with COS
- Creating APIs Connecting to the Mock Backend
- Creating APIs Connecting to the TSF Backend
- Importing APIs
- API Management
- Calling API
- Release and Access
- Custom Domain Name and Certificate
- Usage Plan
- Backend Upstream
- Verification and Security
- Log Statistics
- Access Monitoring
- API Doc Generator
- Application Management
- Permission Management
- Precautions
- Private IP Ranges and Public VIPs of API Gateway Regions
- Plugin Usage
- Best Practices
- Making Serverless Service Available quickly through API Gateway
- Integrating WAF to API Gateway for Security Protection
- Accessing Resources in IDC via API Gateway Dedicated Instance
- Quick Access to TEM Application via API Gateway
- Integrating ECDN to API Gateway for Acceleration
- API Gateway Providing the Access Capability for TKE
- Migrating from Region A to Region B
- Development Guide
- API Documentation
- Legacy Features
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
- Release Notes and Announcements
- Release Notes
- Announcements
- [Important] API Gateway Product Sales Discontinuation Announcement
- [August 30, 2024] Discontinuation Notice for Toronto Region
- [March 1, 2024] Security Management Notice for the Use of Default Domain Name in API Gateway
- [August 15, 2022] Billing of Public Network Outbound Traffic from API Gateway to Backend Services
- Product Introduction
- Purchase Guide
- Getting Started
- Operation Guide
- Instance Management
- Service Management
- Creating API
- API Creation Overview
- Creating APIs Connecting to the Public URL/IP Backend
- Creating APIs Connecting to the VPC Resource Backend
- Creating APIs Connecting to the SCF Backend
- Creating API for Interconnecting Backend with COS
- Creating APIs Connecting to the Mock Backend
- Creating APIs Connecting to the TSF Backend
- Importing APIs
- API Management
- Calling API
- Release and Access
- Custom Domain Name and Certificate
- Usage Plan
- Backend Upstream
- Verification and Security
- Log Statistics
- Access Monitoring
- API Doc Generator
- Application Management
- Permission Management
- Precautions
- Private IP Ranges and Public VIPs of API Gateway Regions
- Plugin Usage
- Best Practices
- Making Serverless Service Available quickly through API Gateway
- Integrating WAF to API Gateway for Security Protection
- Accessing Resources in IDC via API Gateway Dedicated Instance
- Quick Access to TEM Application via API Gateway
- Integrating ECDN to API Gateway for Acceleration
- API Gateway Providing the Access Capability for TKE
- Migrating from Region A to Region B
- Development Guide
- API Documentation
- Legacy Features
- FAQs
- Service Level Agreement
- Contact Us
- Glossary
How to enable private network access for a TKE cluster?
1. Log in to the TKE console, and click Cluster in the left sidebar.
2. Click the ID or name of the desired cluster to go to the cluster details page.
3. Click Basic Information in the left sidebar. You can view information such as the access address, public network/private network access status, and kubeconfig access credential of the cluster in the "Cluster APIServer information" section of the Basic information page.
4. Enable the Private network access. You need to configure a subnet. IP addresses are assigned from the configured subnet after private network access is successfully enabled.
Note:
Do not disable the private network access after you enable it. Otherwise, the API Gateway cannot access the APIServer of the cluster.
How to obtain the TKE cluster admin role?
1. Log in to the TKE console, and click Cluster in the left sidebar.
2. Click the ID or name of the desired cluster to go to the cluster details page.
3. Click Authorization Management > ClusterRole in the left sidebar. Click Get cluster admin role on the page.
4. Failure to obtain the cluster admin role is generally caused by the sub-account not having the Cam permission of the TKE cluster. If this is the case, proceed according to the prompts.
Yes
No
Was this page helpful?