How does TidbClusterAutoScaler continuously monitor resource load and achieve automatic scaling without interruption?

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: TidbClusterAutoScaler 是怎么做到不间断一直监听资源负载并做到自动扩缩的？

| username: HappyUncle

After reviewing the operator code, I didn’t see any logic for repeated coordination. That is, after executing kubectl apply autoscale.yaml, if there are further CPU changes, it will not automatically adjust.

I guess the usage is: write a crontab to periodically execute kubectl apply.

Is that correct?

2
| username: Billmay表妹 | Original post link

I guess you should consult a Kubernetes expert.

3
| username: HappyUncle | Original post link

I found it. At the end of the coordination logic, the autoscale_controller updates the CR status, triggering a k8s event again by modifying the status.

4
| username: Fly-bird | Original post link

Professional, learned a lot.

5
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.