We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suppose I have a deployment with the following config
affinity: nodeAffinity: preferredDuringSchedulingIgnoredDuringExecution: - weight: 100 preference: matchExpressions: - key: topology.kubernetes.io/zone operator: In values: - us-west-2a
Suppose also that:
My understanding is that by default the autoscaler will try to scale up the us-west-2a node group to accommodate this new deployment. Is that correct?
us-west-2a
Now suppose also that us-west-2a (where this deployments wants to be scheduled) suffers an outage and new nodes cannot come online.
Given this hypothetical outage, will the autoscaler eventually realize it needs to scale up a node in a different AZ?
The text was updated successfully, but these errors were encountered:
I'm using the aws autoscaler
Is this cluster-autoscaler or Karpenter?
Sorry, something went wrong.
I'm using the aws autoscaler Is this cluster-autoscaler or Karpenter?
The cluster autoscaler.
/area cluster-autoscaler
No branches or pull requests
Suppose I have a deployment with the following config
Suppose also that:
My understanding is that by default the autoscaler will try to scale up the
us-west-2a
node group to accommodate this new deployment. Is that correct?Now suppose also that
us-west-2a
(where this deployments wants to be scheduled) suffers an outage and new nodes cannot come online.Given this hypothetical outage, will the autoscaler eventually realize it needs to scale up a node in a different AZ?
The text was updated successfully, but these errors were encountered: