Comments (8)
Hi @MaciekPytel. I found out a similar issue in #3852 but then got impression that CA does ignore extended resources which are unfamiliar to it and move on with scaling up. Has that behavior changed recently?
from autoscaler.
@x13n any thoughts on this?
from autoscaler.
CA will observe other nodes in a node group to get an idea how new nodes will look like - if they contain extended resources that are later required by a pod, a scale up should get triggered. However, if there are no nodes or if there's a mix of node with and without the extended resource, CA will have no idea about such extended resource and won't trigger scale up because it will think it won't help the pod.
from autoscaler.
bserve other nodes in a node group
Is there way to tell CA to ignore the resources it is unaware of ?
from autoscaler.
I don't think so - why do you ask? What would be the use case for ignoring some resources?
from autoscaler.
I don't think so - why do you ask? What would be the use case for ignoring some resources?
In my situation, there's a controller in place that adds extended resources to new nodes. These extended resources are later requested by some pods, just like the native resources CPU and memory. Let's take an example: imagine I have two nodes in my cluster that are almost maxed out, leaving no free resources for new pods. Now, I want to create a workload Pod that requests extended resources. The CA realizes it can't fit these Pods onto existing nodes due to the resource shortage (in this case, the extended resources like example.com/myresource
). Since the CA doesn't recognize these extended resources, it would be helpful if it could still proceed with creating new nodes. Meanwhile, my external controller would continue its job of adding the extended resources to the nodes. Currently, these pods remain pending because there's no node with enough extended resources, and the CA can't create new nodes.
from autoscaler.
If CA ignored extended resources on both pods and nodes, it could scale a node group that won't have the extended resource later on. Or it could also create nodes for pods requesting, say, example.com/myresource: 1000
, even though your controller can only set the allocatable up to, say, example.com/myresource: 10
. Or it could create nodes with example.com/myresource
even though the pod requested example.com/myotherresource
. Such pods would stay pending, only now there will also be an empty node around. I guess in a controlled environment you could ensure these edge conditions won't happen, so some kind of optional feature in CA might make sense. On the other hand, isn't this a use case for Dynamic Resource Allocation? Current version doesn't really work with autoscaling, but IIUC there is ongoing work to make it compatible.
from autoscaler.
Related Issues (20)
- Cluster autoscaler is not able to scale down Rancher managed cluster once OpenStack quota were reached HOT 2
- CVE-2023-48795 HOT 3
- cluster-autoscaler clusterapi provider performance degrades when there are a high number of node groups HOT 4
- Helm functionnal for Rancher with cloudconfig in a secret HOT 1
- Cluster AutoScaler terminates on demand instances, leading to replace spot instance with new on demand instance, causing terminated pods.
- VPA Not able to detect Prometheus StatefulSet HOT 3
- scale down issue with scale-down-utilization-threshold at 0 HOT 1
- is it possible 502 raise sometimes, during node evict/drain.
- Cluster-Autoscaler decrease AWS AutoScalingGroup desired capacity during unregistered nodes removal that causes unneeded shriking of the ASG HOT 1
- Broken link in cluster-autoscaler FAQ.md HOT 3
- When using examples/helmster.yaml for testing, the updater component experienced a panic, with the panic message being runtime error: invalid memory address or nil pointer dereference HOT 7
- cluster-autoscaler fails to backoff when max-node-provision-time is 5 minutes leaving orphaned EC2 instance requiring manual termination HOT 1
- Implement Check-capacity Provisioning Class HOT 8
- Implement AtomicScaleUp ProvisioningClass HOT 5
- VPA doesn't accept `1.2Gi` in `.spec.ResourcePolicy.MinAllowed` HOT 7
- VPA updater only works initially HOT 1
- Missing status subresource when using custom VPA recommender with GKE native VPA setup HOT 7
- Upgrade Autoscaler Components to use Debian 12 Distroless
- Release vpa 1.1.2 HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from autoscaler.