Release Notes
Announcements
Release Notes
ingress.cloud.tencent.com/enable-group: 'true' annotation when creating Ingress resources, and use the kubernetes.io/ingress.existLbId: lb-xxxxxxxx annotation to point to the same CLB instance.kube-system namespace and check the VERSION parameter in the configmap tke-service-controller-config and tke-ingress-controller-config to obtain the version information of the respective components.EnableIngressController parameter in tke-service-controller-config is set to 'true', it indicates that the converged version mode is enabled.ingress.cloud.tencent.com/enable-group: 'true' must be specified together with kubernetes.io/ingress.existLbId: lb-xxxxxxxx when the Ingress is created. Adding the annotation to an existing Ingress will not enable the feature.apiVersion: v1kind: Namespacemetadata:name: ns1---apiVersion: v1kind: Namespacemetadata:name: ns2---apiVersion: networking.k8s.io/v1kind: Ingressmetadata:annotations:ingress.cloud.tencent.com/listen-ports: '[{"HTTP": 80}]'kubernetes.io/ingress.existLbId: lb-xxxxxxxx # should be replaced with your own clb idingress.cloud.tencent.com/enable-group: 'true' # must be specified at ingress creation timename: nginx-ingress-1namespace: ns1spec:rules:- http:paths:- backend:service:name: nginx-serviceport:number: 80path: /pathType: ImplementationSpecific---apiVersion: networking.k8s.io/v1kind: Ingressmetadata:annotations:ingress.cloud.tencent.com/listen-ports: '[{"HTTP": 81}]'kubernetes.io/ingress.existLbId: lb-xxxxxxxx # should be replaced with your own clb idingress.cloud.tencent.com/enable-group: 'true'name: nginx-ingress-2namespace: ns2spec:rules:- http:paths:- backend:service:name: nginx-serviceport:number: 80path: /pathType: ImplementationSpecific
apiVersion: v1kind: Namespacemetadata:name: ns1---apiVersion: v1kind: Namespacemetadata:name: ns2---apiVersion: networking.k8s.io/v1kind: Ingressmetadata:annotations:ingress.cloud.tencent.com/listen-ports: '[{"HTTP": 80}]'kubernetes.io/ingress.existLbId: lb-xxxxxxxx # should be replaced with your own clb idingress.cloud.tencent.com/enable-group: 'true' # must be specified together with kubernetes.io/ingress.existLbId when creating a new ingresskubernetes.io/ingress.http-rules: '[{"host":"example.com","path":"/api","backend":{"serviceName":"anyserver","servicePort":"80"}},{"host":"example.com","path":"/tmp","rewrite":{"port":80,"host":"example.com","path":"/api"}}]'kubernetes.io/ingress.https-rules: "null"kubernetes.io/ingress.rule-mix: "true"name: nginx-ingress-1namespace: ns1spec:rules:- http:paths:- backend:service:name: nginx-serviceport:number: 80path: /pathType: ImplementationSpecific---apiVersion: networking.k8s.io/v1kind: Ingressmetadata:annotations:ingress.cloud.tencent.com/listen-ports: '[{"HTTP": 80}]'kubernetes.io/ingress.existLbId: lb-xxxxxxxx # should be replaced with your own clb idingress.cloud.tencent.com/enable-group: 'true'name: nginx-ingress-2namespace: ns2spec:rules:- http:paths:- backend:service:name: nginx-serviceport:number: 80path: /homepathType: ImplementationSpecific
# Example: Different Ingresses reuse the same CLB listener, each using a different domain# Note:# - Two Ingresses are in different namespaces (ns1 and ns2)# - Reuse the same CLB (specified by kubernetes.io/ingress.existLbId)# - Reuse the same listener ports (80 and 8080)# - Each routes traffic using a different domain# - The Ingress in ns1 uses the domain: app1.example.com# - The Ingress in ns2 uses the domain: app2.example.comapiVersion: v1kind: Namespacemetadata:name: ns1---apiVersion: v1kind: Namespacemetadata:name: ns2---# Ingress 1: uses the domain app1.example.comapiVersion: networking.k8s.io/v1kind: Ingressmetadata:annotations:ingress.cloud.tencent.com/listen-ports: '[{"HTTP": 80}]'ingress.cloud.tencent.com/enable-group: 'true'kubernetes.io/ingress.existLbId: lb-xxxxxxxx # should be replaced with your own lbidname: app1-ingressnamespace: ns1spec:rules:- host: app1.example.comhttp:paths:- backend:service:name: app1-serverport:number: 80path: /pathType: Prefix---# Ingress 2: uses the domain app2.example.com (reuses the same CLB and listener)apiVersion: networking.k8s.io/v1kind: Ingressmetadata:annotations:ingress.cloud.tencent.com/listen-ports: '[{"HTTP": 80}]'ingress.cloud.tencent.com/enable-group: 'true'kubernetes.io/ingress.existLbId: lb-xxxxxxxx # should be replaced with your own lbid (same as above)name: app2-ingressnamespace: ns2spec:rules:- host: app2.example.comhttp:paths:- backend:service:name: app2-serverport:number: 80path: /pathType: Prefix---# ns1's ServiceapiVersion: v1kind: Servicemetadata:name: app1-servernamespace: ns1labels:app: app1-serverspec:ports:- name: httpport: 80targetPort: 80selector:app: app1-servertype: NodePort---# ns1's DeploymentapiVersion: apps/v1kind: Deploymentmetadata:name: app1-servernamespace: ns1spec:replicas: 1selector:matchLabels:app: app1-servertemplate:metadata:labels:app: app1-serverspec:containers:- image: ccr.ccs.tencentyun.com/paas/anyservername: anyserverenv:- name: POD_NAMEvalueFrom:fieldRef:apiVersion: v1fieldPath: metadata.name---# ns2's ServiceapiVersion: v1kind: Servicemetadata:name: app2-servernamespace: ns2labels:app: app2-serverspec:ports:- name: httpport: 80targetPort: 80selector:app: app2-servertype: NodePort---# ns2's DeploymentapiVersion: apps/v1kind: Deploymentmetadata:name: app2-servernamespace: ns2spec:replicas: 1selector:matchLabels:app: app2-servertemplate:metadata:labels:app: app2-serverspec:containers:- image: ccr.ccs.tencentyun.com/paas/anyservername: anyserverenv:- name: POD_NAMEvalueFrom:fieldRef:apiVersion: v1fieldPath: metadata.name
Annotation | Description | Whether it is supported (in reuse scenarios) |
ingress.cloud.tencent.com/listen-ports | Custom listening port | Supported |
ingress.cloud.tencent.com/direct-access | Enable CLB passthrough to Pod | Supported |
ingress.cloud.tencent.com/auto-rewrite | Use automatic redirection | Supported |
kubernetes.io/ingress.rule-mix | Enable hybrid (http/https) protocol | Supported |
kubernetes.io/ingress.http-rules | http protocol | Supported |
kubernetes.io/ingress.https-rules | https protocol | Supported |
ingress.cloud.tencent.com/enable-grace-deletion | Graceful Deletion of Pod | Supported |
ingress.cloud.tencent.com/lb-rs-weight | Customize backend RS weight | Supported |
ingress.cloud.tencent.com/tke-service-config | Use manual scaling configuration | Supported |
ingress.cloud.tencent.com/pass-to-target | bypass by default | Supported |
ingress.cloud.tencent.com/tke-service-config-auto | Use automatically generated scaling configuration | Not supported. |
ingress.cloud.tencent.com/rewrite-support | Use manual redirection | Deprecated. |
ingress.cloud.tencent.com/rewrite-supportkubernetes.io/ingress.http-rules and kubernetes.io/ingress.https-rules without adding this annotation.ingress.cloud.tencent.com/auto-rewritefalse both indicate disabling automatic redirection.ingress.cloud.tencent.com/enable-group: 'true' to existing Ingresses.ingress.cloud.tencent.com/status.conditions: '[{"type":"Ready","status":"True","lastTransitionTime":"2025-10-07T11:30:53Z","reason":"Success","message":""}]'
ingress.cloud.tencent.com/status.conditions: '[{"type":"Ready","status":"False","lastTransitionTime":"2025-10-07T11:35:10Z","reason":"ListenerError","message":"SyncClientError\\nErrorCode: E4403\\nDetails: Group: lb-fgim8ppi. The loadbalancerhas port conflict in the listeners 80_HTTP.\\nOriginError: ingress ns1/server2listener 80_HTTP domain example.com's path / conflict: already owned by ns1/server1\\n"}]'
ingress.cloud.tencent.com/enable-group: 'true' annotation). An error example is shown below:ingress.cloud.tencent.com/status.conditions: '[{"type":"Ready","status":"False","lastTransitionTime":"2025-10-09T12:29:05Z","reason":"LoadbalancerError","message":"SyncClientError\\nErrorCode: E4406\\nDetails: Group: lb-fgim8ppi. Can not use lb:ns1/server1 used by another ingress/multiClusterIngress .\\nOriginError:group can't reuse clb with ingress which has existLbId, please process\\n"}]'
ingress.cloud.tencent.com/status.conditions: '[{"type":"Ready","status":"False","lastTransitionTime":"2025-10-09T12:40:01Z","reason":"LoadbalancerError","message":"SyncClientError\\nErrorCode: E4407\\nDetails: Group: lb-fgim8ppi. Can not use lb:lb-fgim8ppi used by another service ns1/svc1.\\nOriginError: ingress managered by group not support reuse clb with service\\n"}]'
Apakah halaman ini membantu?
Anda juga dapat Menghubungi Penjualan atau Mengirimkan Tiket untuk meminta bantuan.
masukan