cluster-autoscaling -> node-autoscaling clean-up
301 redirect added, and a bunch of references on other pages renamed.pull/45802/head
Kuba Tużnik
parent
7c99a67b36
commit
dc530ffd6a
|
|
@ -357,7 +357,7 @@ Learn more about the following:
|
|||
* [Node](https://git.k8s.io/design-proposals-archive/architecture/architecture.md#the-kubernetes-node)
|
||||
section of the architecture design document.
|
||||
* [Graceful/non-graceful node shutdown](/docs/concepts/cluster-administration/node-shutdown/).
|
||||
* [Cluster autoscaling](/docs/concepts/cluster-administration/cluster-autoscaling/) to
|
||||
* [Node autoscaling](/docs/concepts/cluster-administration/node-autoscaling/) to
|
||||
manage the number and size of nodes in your cluster.
|
||||
* [Taints and Tolerations](/docs/concepts/scheduling-eviction/taint-and-toleration/).
|
||||
* [Node Resource Managers](/docs/concepts/policy/node-resource-managers/).
|
||||
|
|
|
|||
|
|
@ -52,7 +52,7 @@ Before choosing a guide, here are some considerations:
|
|||
## Managing a cluster
|
||||
|
||||
* Learn how to [manage nodes](/docs/concepts/architecture/nodes/).
|
||||
* Read about [cluster autoscaling](/docs/concepts/cluster-administration/cluster-autoscaling/).
|
||||
* Read about [Node autoscaling](/docs/concepts/cluster-administration/node-autoscaling/).
|
||||
|
||||
* Learn how to set up and manage the [resource quota](/docs/concepts/policy/resource-quotas/) for shared clusters.
|
||||
|
||||
|
|
|
|||
|
|
@ -466,7 +466,7 @@ common use cases and suggested solutions.
|
|||
- Or, run an internal private registry behind your firewall with open read access.
|
||||
- No Kubernetes configuration is required.
|
||||
- Use a hosted container image registry service that controls image access
|
||||
- It will work better with cluster autoscaling than manual node configuration.
|
||||
- It will work better with Node autoscaling than manual node configuration.
|
||||
- Or, on a cluster where changing the node configuration is inconvenient, use `imagePullSecrets`.
|
||||
1. Cluster with proprietary images, a few of which require stricter access control.
|
||||
- Ensure [AlwaysPullImages admission controller](/docs/reference/access-authn-authz/admission-controllers/#alwayspullimages)
|
||||
|
|
|
|||
|
|
@ -618,7 +618,7 @@ section of the enhancement proposal about Pod topology spread constraints.
|
|||
because, in this case, those topology domains won't be considered until there is
|
||||
at least one node in them.
|
||||
|
||||
You can work around this by using a cluster autoscaling tool that is aware of
|
||||
You can work around this by using a Node autoscaler that is aware of
|
||||
Pod topology spread constraints and is also aware of the overall set of topology
|
||||
domains.
|
||||
|
||||
|
|
|
|||
|
|
@ -129,7 +129,7 @@ its [`Cron` scaler](https://keda.sh/docs/latest/scalers/cron/). The `Cron` scale
|
|||
If scaling workloads isn't enough to meet your needs, you can also scale your cluster infrastructure itself.
|
||||
|
||||
Scaling the cluster infrastructure normally means adding or removing {{< glossary_tooltip text="nodes" term_id="node" >}}.
|
||||
Read [cluster autoscaling](/docs/concepts/cluster-administration/cluster-autoscaling/)
|
||||
Read [Node autoscaling](/docs/concepts/cluster-administration/node-autoscaling/)
|
||||
for more information.
|
||||
|
||||
## {{% heading "whatsnext" %}}
|
||||
|
|
@ -139,4 +139,4 @@ for more information.
|
|||
- [HorizontalPodAutoscaler Walkthrough](/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/)
|
||||
- [Resize Container Resources In-Place](/docs/tasks/configure-pod-container/resize-container-resources/)
|
||||
- [Autoscale the DNS Service in a Cluster](/docs/tasks/administer-cluster/dns-horizontal-autoscaling/)
|
||||
- Learn about [cluster autoscaling](/docs/concepts/cluster-administration/cluster-autoscaling/)
|
||||
- Learn about [Node autoscaling](/docs/concepts/cluster-administration/node-autoscaling/)
|
||||
|
|
|
|||
|
|
@ -49,7 +49,7 @@ Cluster administrator actions include:
|
|||
|
||||
- [Draining a node](/docs/tasks/administer-cluster/safely-drain-node/) for repair or upgrade.
|
||||
- Draining a node from a cluster to scale the cluster down (learn about
|
||||
[Cluster Autoscaling](https://github.com/kubernetes/autoscaler/#readme)).
|
||||
[Node Autoscaling]((/docs/concepts/cluster-administration/node-autoscaling/)).
|
||||
- Removing a pod from a node to permit something else to fit on that node.
|
||||
|
||||
These actions might be taken directly by the cluster administrator, or by automation
|
||||
|
|
|
|||
|
|
@ -121,7 +121,7 @@ Learn more about [Vertical Pod Autoscaler](https://github.com/kubernetes/autosca
|
|||
and how you can use it to scale cluster
|
||||
components, including cluster-critical addons.
|
||||
|
||||
* Read about [cluster autoscaling](/docs/concepts/cluster-administration/cluster-autoscaling/)
|
||||
* Read about [Node autoscaling](/docs/concepts/cluster-administration/node-autoscaling/)
|
||||
|
||||
* The [addon resizer](https://github.com/kubernetes/autoscaler/tree/master/addon-resizer#readme)
|
||||
helps you in resizing the addons automatically as your cluster's scale changes.
|
||||
|
|
|
|||
|
|
@ -183,7 +183,7 @@ simply as *nodes*).
|
|||
to help determine how many nodes you need, based on the number of pods and
|
||||
containers you need to run. If you are managing nodes yourself, this can mean
|
||||
purchasing and installing your own physical equipment.
|
||||
- *Autoscale nodes*: Read [Cluster Autoscaling](/docs/concepts/cluster-administration/cluster-autoscaling) to learn about the
|
||||
- *Autoscale nodes*: Read [Node Autoscaling](/docs/concepts/cluster-administration/node-autoscaling) to learn about the
|
||||
tools available to automatically manage your nodes and the capacity they
|
||||
provide.
|
||||
- *Set up node health checks*: For important workloads, you want to make sure
|
||||
|
|
|
|||
|
|
@ -597,7 +597,7 @@ guidelines, which cover this exact use case.
|
|||
## {{% heading "whatsnext" %}}
|
||||
|
||||
If you configure autoscaling in your cluster, you may also want to consider using
|
||||
[cluster autoscaling](/docs/concepts/cluster-administration/cluster-autoscaling/)
|
||||
[node autoscaling](/docs/concepts/cluster-administration/node-autoscaling/)
|
||||
to ensure you are running the right number of nodes.
|
||||
|
||||
For more information on HorizontalPodAutoscaler:
|
||||
|
|
|
|||
|
|
@ -54,6 +54,7 @@
|
|||
/docs/concepts/cluster-administration/access-cluster/ /docs/tasks/access-application-cluster/access-cluster/ 301
|
||||
/docs/concepts/cluster-administration/audit/ /docs/tasks/debug/debug-cluster/audit/ 301
|
||||
/docs/concepts/cluster-administration/authenticate-across-clusters-kubeconfig /docs/tasks/access-application-cluster/authenticate-across-clusters-kubeconfig/ 301
|
||||
/docs/concepts/cluster-administration/cluster-autoscaling/ /docs/concepts/cluster-administration/node-autoscaling/ 301
|
||||
/docs/concepts/cluster-administration/cluster-management/ /docs/tasks/administer-cluster/ 302
|
||||
/docs/concepts/cluster-administration/configure-etcd/ /docs/tasks/administer-cluster/configure-upgrade-etcd/ 301
|
||||
/docs/concepts/cluster-administration/device-plugins/ /docs/concepts/extend-kubernetes/compute-storage-net/device-plugins/ 301
|
||||
|
|
|
|||
Loading…
Reference in New Issue