Tencent Kubernetes Engine
- Release Notes and Announcements
- Release Notes
- Announcements
- Security Vulnerability Fix Description
- Release Notes
- Kubernetes Version Maintenance
- Runtime Version Maintenance Description
- Product Introduction
- Quick Start
- TKE General Cluster Guide
- Purchase a TKE General Cluster
- Permission Management
- Controlling TKE cluster-level permissions
- TKE Kubernetes Object-level Permission Control
- Cluster Management
- Images
- Worker node introduction
- Normal Node Management
- Native Node Management
- Purchasing Native Nodes
- Supernode management
- Purchasing a Super Node
- Registered Node Management
- Memory Compression Instructions
- GPU Share
- qGPU Online/Offline Hybrid Deployment
- Kubernetes Object Management
- Workload
- Configuration
- Auto Scaling
- Service Management
- Ingress Management
- CLB Type Ingress
- API Gateway Type Ingress
- Storage Management
- Use File to Store CFS
- Use Cloud Disk CBS
- Add-On Management
- CBS-CSI Description
- Network Management
- GlobalRouter Mode
- VPC-CNI Mode
- Static IP Address Mode Instructions
- Cilium-Overlay Mode
- OPS Center
- Audit Management
- Event Management
- Log Management
- Using CRD to Configure Log Collection
- Backup Center
- TKE Serverless Cluster Guide
- Purchasing a TKE Serverless Cluster
- TKE Serverless Cluster Management
- Super Node Management
- Kubernetes Object Management
- OPS Center
- Log Collection
- Using a CRD to Configure Log Collection
- Audit Management
- Event Management
- TKE Registered Cluster Guide
- Registered Cluster Management
- Ops Guide
- TKE Insight
- TKE Scheduling
- Job Scheduling
- Native Node Dedicated Scheduler
- Cloud Native Service Guide
- Practical Tutorial
- Cluster
- Serverless Cluster
- Mastering Deep Learning in Serverless Cluster
- Scheduling
- Security
- Service Deployment
- Proper Use of Node Resources
- Network
- DNS
- Self-Built Nginx Ingress Practice Tutorial
- Logs
- Monitoring
- OPS
- DevOps
- Construction and Deployment of Jenkins Public Network Framework Appications based on TKE
- Auto Scaling
- KEDA
- Containerization
- Microservice
- Cost Management
- Hybrid Cloud
- Fault Handling
- Pod Status Exception and Handling
- Pod exception troubleshooter
- API Documentation
- Making API Requests
- Elastic Cluster APIs
- Resource Reserved Coupon APIs
- Cluster APIs
- Third-party Node APIs
- Network APIs
- Node APIs
- Node Pool APIs
- TKE Edge Cluster APIs
- Cloud Native Monitoring APIs
- Super Node APIs
- TKE API 2022-05-01
- Making API Requests
- Node Pool APIs
- FAQs
- TKE General Cluster
- TKE Serverless Cluster
- About OPS
- Service Agreement
- User Guide(Old)
DocumentationTencent Kubernetes EnginePractical TutorialNetworkSelf-Built Nginx Ingress Practice TutorialHigh Availability Configuration Optimization
High Availability Configuration Optimization
Last updated: 2024-08-12 17:48:23
Overview
This document describes the high-availability deployment configuration methods for Nginx Ingress.
Increasing the Number of Replicas
Configure automatic scaling:
controller:autoscaling:enabled: trueminReplicas: 10maxReplicas: 100targetCPUUtilizationPercentage: 50targetMemoryUtilizationPercentage: 50behavior: # Quick scale-out to handle traffic peaks, slow scale-in to leave a buffer to avoid abnormal trafficscaleUp:stabilizationWindowSeconds: 300policies:- type: Percentvalue: 900periodSeconds: 15 # Allowing scale-out up to 9 times the current number of replicas every 15 secondsscaleDown:stabilizationWindowSeconds: 300policies:- type: Podsvalue: 1periodSeconds: 600 # Allowing scale-in of only one pod at most every 10 minutes
If you want a fixed number of replicas, directly configure
replicaCount:controller:replicaCount: 50
Spreading Scheduling
Use topology distribution constraints to spread out pods for disaster recovery and avoid single points of failure:
controller:topologySpreadConstraints: # Policy to maximize spreading- labelSelector:matchLabels:app.kubernetes.io/name: '{{ include "ingress-nginx.name" . }}'app.kubernetes.io/instance: '{{ .Release.Name }}'app.kubernetes.io/component: controllertopologyKey: topology.kubernetes.io/zonemaxSkew: 1whenUnsatisfiable: ScheduleAnyway- labelSelector:matchLabels:app.kubernetes.io/name: '{{ include "ingress-nginx.name" . }}'app.kubernetes.io/instance: '{{ .Release.Name }}'app.kubernetes.io/component: controllertopologyKey: kubernetes.io/hostnamemaxSkew: 1whenUnsatisfiable: ScheduleAnyway
Scheduling to Dedicated Nodes
Typically, the load of Nginx Ingress Controller is proportional to the traffic. Considering its importance as a gateway, we recommend scheduling it to dedicated nodes or super nodes to avoid interfering with business pods or being interfered by them.
Schedule it to the specified node pool:
controller:nodeSelector:tke.cloud.tencent.com/nodepool-id: np-********
Note:
Super nodes perform better as all pods exclusively occupy the virtual machine without mutual interference. If you are using a serverless cluster, there is no need to configure the scheduling policy here, as it will only be scheduled to super nodes.
Setting Reasonable requests and limits
If Nginx Ingress is not scheduled to super nodes, set requests and limits reasonably to ensure sufficient resources while avoiding excessive resource usage that leads to high node load:
controller:resources:requests:cpu: 500mmemory: 512Milimits:cpu: 1000mmemory: 1Gi
If you are using super nodes or a serverless cluster, you need to define requests only, that is, declare the virtual machine specifications for each pod:
controller:resources:requests:cpu: 1000mmemory: 2Gi
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No