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

CLB Ingress Creation Error

PDF
Focus Mode
Font Size
Last updated: 2024-12-13 14:48:39

Issue

Error E6009 was reported when I created a CLB Ingress.


Possible Causes

ingress-nginx (Nginx Ingress community edition) versions earlier than v1.0.0 don't support validating webhook callbacks for resources of the networking.k8s.io/v1 type. You need to remove v1 resource validation from validation CRDs.

Solutions

You can solve this problem in the following ways:

Option 1. Cancel v1 resource validation

Change the apiVersions field in webhooks.rules of resources of the validatingwebhookconfigurations type to v1beta1.
1. Log in to the TKE console and select the region of your cluster.
2. On the Cluster Management page, click the name of the target cluster to enter its details page.
3. Select Kubernetes resource manager on the left sidebar and search for validatingwebhookconfigurations on the Resource Type page.

4. Select validatingwebhookconfigurations from the search results and click Edit YAML on the right of the resource object list to check whether the apiVersions field in webhooks.rules of each resource object is v1beta1.

5. Upgrade the add-on. The above steps solve the resource validation problem of an existing Nginx Ingress instance. To avoid similar problems with new instances, you need to upgrade the Nginx Ingress add-on as follows:
5.1 On the cluster details page, select Add-On Management on the left sidebar.
5.2 Click Upgrade on the right of Nginx Ingress to upgrade it to v1.1.0.

Option 2. Cancel resource validation

1. Log in to the TKE console and select the region of your cluster.
2. On the Cluster Management page, click the name of the target cluster to enter its details page.
3. Select Kubernetes resource manager on the left sidebar and search for validatingwebhookconfigurations on the Resource Type page.
4. Select validatingwebhookconfigurations from the search results and click Delete on the right of the resource object list.
5. Upgrade the add-on. The above steps solve the resource validation problem of an existing Nginx Ingress instance. To avoid similar problems with new instances, you need to upgrade the Nginx Ingress add-on as follows:
5.1 On the cluster details page, select Add-On Management on the left sidebar.
5.2 Click Upgrade on the right of Nginx Ingress to upgrade it to v1.1.0.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback