daimaxiaxie

都2020年了还没修复。。。 还可以设置 ``` lineStyle: { color: 'white', } ```

In the code, the utilization calculation is like this: `(CPU requests not include Daemonset's Pod) / (CPU Allocatable - daemonset's pod requests)` https://github.com/kubernetes/autoscaler/blob/c96aa9b97087603cb6884e1af7c20fa2969fb86d/cluster-autoscaler/simulator/utilization/info.go#L125

Maybe higher version of ‘skipNodesWithCustomControllerPods’ option is useful.

The problem is not just AWS, it also exists on other clouds. For example AliCloud. The root of the problem is that scaling activities on the cloud are asynchronous.

> I don't think there is much value in limiting the total number of connections. If there are too many connections, it will only affect the speed of configuration push....

> Also, can we use `DiscoveryServer.adsClients` to count the number of connections? No, `DiscoveryServer.adsClients` change in stream handler. It is not synchronized with grpc's dial time.

We need to strengthen the mapping relationship between NodeClaim and EC2. To better manage elastic instances. *ASG is gone.* A possible solution: 1. Fill NodeClaim.UID in EC2 tag during launch....

When I use Karpenter with AWS: Stop `nodeclaimgarbagecollection` in AWS provider, add panic in Karpenter. 1. before panic ```bash $ kubectl get nodeclaims.karpenter.sh No resources found $ kubectl get nodes...

Yes, I'm just testing it right now. It's not an urgent issue.

@ellistarn We redefined the value of `topology.kubernetes.io/zone`. However, the current zone value is provided by the CloudProvider. Is it possible to support custom `topology.kubernetes.io/zone` and other WellKnownLabel values?