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

Deploying KEDA on TKE

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2024-12-24 15:51:36

Adding helm repo

To deploy KEDA on TKE, it is required to add KEDA's Helm repository by using the following command:
helm repo add kedacore https://kedacore.github.io/charts
helm repo update

Preparing values.yaml

Next, you can check the default values.yaml file to understand the customizable configuration items by using the following command:
helm show values kedacore/keda
Since the default dependency images cannot be pulled in the Chinese mainland environment, you can replace them with mirror images from Docker Hub and configure them in the values.yaml file. For example:
image:
keda:
registry: docker.io
repository: imroc/keda
metricsApiServer:
registry: docker.io
repository: imroc/keda-metrics-apiserver
webhooks:
registry: docker.io
repository: imroc/keda-admission-webhooks
Note:
The above image will be automatically synchronized for a long time, so you can use and update it with confidence.

Installation

Use the following command to install KEDA:
helm upgrade --install keda kedacore/keda \\
--namespace keda --create-namespace \\
-f values.yaml

Versions and Upgrades

Each version of KEDA is compatible with specific Kubernetes versions. Before installing KEDA, you need to confirm whether the TKE cluster version is compatible with the KEDA version you want to install. You can check KEDA Kubernetes Compatibility to confirm which KEDA versions are compatible with your current cluster version.
For example, if the TKE cluster version is 1.26 and the latest compatible KEDA version is v2.12, the highest Chart version (CHART VERSION) compatible with KEDA v2.12 (APP VERSION) is 2.12.1:
$ helm search repo keda --versions
NAME CHART VERSION APP VERSION DESCRIPTION
kedacore/keda 2.13.2 2.13.1 Event-based autoscaler for workloads on Kubernetes
kedacore/keda 2.13.1 2.13.0 Event-based autoscaler for workloads on Kubernetes
kedacore/keda 2.13.0 2.13.0 Event-based autoscaler for workloads on Kubernetes
kedacore/keda 2.12.1 2.12.1 Event-based autoscaler for workloads on Kubernetes
kedacore/keda 2.12.0 2.12.0 Event-based autoscaler for workloads on Kubernetes
kedacore/keda 2.11.2 2.11.2 Event-based autoscaler for workloads on Kubernetes
kedacore/keda 2.11.1 2.11.1 Event-based autoscaler for workloads on Kubernetes
Specify the version when installing KEDA:
helm upgrade --install keda kedacore/keda \\
--namespace keda --create-namespace \\
--version 2.12.1 \\
-f values.yaml
You can reuse the above installation command for future upgrade versions by simply modifying the version number.
Note:
Before upgrading the TKE cluster, use the above method to check if the upgraded cluster version is compatible with the current version of KEDA. If not, please upgrade KEDA to the latest version compatible with the current cluster version in advance.

Uninstallation

For specific steps, please refer to Official Uninstall Instructions.

References




Ajuda e Suporte

Esta página foi útil?

comentários