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

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

Glossary

Overview

PDF

Mode fokus

Ukuran font

Terakhir diperbarui: 2024-12-23 11:30:47

Services expose TKE in clusters based on the layer-4 network. Exposed service types, such as ClusterIP, NodePort, and LoadBalancer, are all based on the access entry of layer-4 network services. They lack layer-7 network capabilities, such as load balancing, SSL, and name-based virtual hosts. An Ingress exposes HTTP and HTTPS services in the layer-7 network and provides common layer-7 network capabilities.
Basic Ingress Concepts
An Ingress is a collection of rules that allow access to services of a cluster. You can configure different forwarding rules to allow different URLs to access different services. To properly run Ingress resources, the cluster must run an Ingress controller. TKE enables the CLB-based TKE Ingress Controller by default in the cluster.
Ingress Lifecycle Management
The external service capability of an Ingress depends on resources provided by the CLB. Service resource management is one of the important feature of an Ingress. The following table describes the labels that an Ingress will use for resource lifecycle management.
Label
Description
tke-createdBy-flag = yes
Indicates that the resource was created by TKE. When an Ingress with this label is deleted, the corresponding resources are also deleted.
When an Ingress without this label is destroyed, only the CLB listener is deleted and the CLB will not be deleted.
tke-clusterId = <clusterId>
Identifies the cluster that uses the resource.
When the Ingress is deleted, the corresponding label (with correct ClusterId) will be deleted.
tke-lb-ingress-uuid = <Ingress UUID>
Identifies the Ingress that uses the resource.
Currently, an Ingress cannot reuse a CLB with other Ingresses. If you specify that an Ingress use an existing CLB but the label value is incorrect, the request will be rejected.
When the Ingress is deleted, the corresponding label (with correct Ingress UUID) will be deleted.
﻿
Ingress Controller Usage Method
In addition to TKE Ingress Controller provided by Tencent Cloud, the Kubernetes community has various third-party Ingress controllers. These Ingress controllers expose services in the layer-7 network. The Kubernetes community allows you to use the kubernetes.io/ingress.class annotation to distinguish different Ingress controllers and determine the controller that processes an ingress. TKE Ingress Controller also supports this annotation. The detailed rules and use suggestions are as follows:
When an Ingress does not have the kubernetes.io/ingress.class annotation, TKE Ingress Controller will manage the Ingress.
When an Ingress has the kubernetes.io/ingress.class annotation and its value is qcloud, TKE Ingress Controller will manage the Ingress.
When an Ingress modifies the kubernetes.io/ingress.class annotation content, TKE Ingress Controller will add the Ingress to or remove it from its management scope based on the annotation content. This operation will create or release an Ingress.
When TKE Ingress Controller is not required, you can change the number of Deployment (kube-system:l7-lb-controller) replicas in the cluster to 0 to disable the TKE Ingress Controller feature.
Note: 
Before disabling the TKE Ingress Controller feature, ensure that no Ingress is managed by TKE Ingress Controller to prevent CLB release failures.
If Deletion Protection is enabled or a private connection is used for the CLB, the CLB will not be deleted when services are deleted.
Ingress Operations
For more information about Ingress-related operations and features, see the following documents:
Basic Ingress Features
Using an Existing CLB for Direct Pod Connection
Using TKEServiceConfig to Configure CLBs
Mixed Use of HTTP and HTTPS Protocols through Ingress
Ingress Certificate Configuration
﻿

Bantuan dan Dukungan

Apakah halaman ini membantu?

Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.

masukan

tencent cloud

Tencent Kubernetes Engine

Overview

Basic Ingress Concepts

Ingress Lifecycle Management

Ingress Controller Usage Method

Ingress Operations

Bantuan dan Dukungan

Label	Description
tke-createdBy-flag = yes	Indicates that the resource was created by TKE. When an Ingress with this label is deleted, the corresponding resources are also deleted. When an Ingress without this label is destroyed, only the CLB listener is deleted and the CLB will not be deleted.
tke-clusterId = <clusterId>	Identifies the cluster that uses the resource. When the Ingress is deleted, the corresponding label (with correct ClusterId) will be deleted.
tke-lb-ingress-uuid = <Ingress UUID>	Identifies the Ingress that uses the resource. Currently, an Ingress cannot reuse a CLB with other Ingresses. If you specify that an Ingress use an existing CLB but the label value is incorrect, the request will be rejected. When the Ingress is deleted, the corresponding label (with correct Ingress UUID) will be deleted.