Merge pull request #24415 from sftim/20201007_remove_cluster_management_task

Remove cluster management task

Author: k8s-ci-robot

content/en/blog/_posts/2019-04-16-pod-priority-and-preemption-in-kubernetes.md

@@ -12,7 +12,7 @@ Kubernetes is well-known for running scalable workloads. It scales your workload
 
 ## Guaranteed scheduling with controlled cost
 
-[Kubernetes Cluster Autoscaler](https://kubernetes.io/docs/tasks/administer-cluster/cluster-management/#cluster-autoscaling) is an excellent tool in the ecosystem which adds more nodes to your cluster when your applications need them. However, cluster autoscaler has some limitations and may not work for all users:
+[Kubernetes Cluster Autoscaler](https://github.com/kubernetes/autoscaler/) is an excellent tool in the ecosystem which adds more nodes to your cluster when your applications need them. However, cluster autoscaler has some limitations and may not work for all users:
 
 - It does not work in physical clusters.
 - Adding more nodes to the cluster costs more.

content/en/docs/concepts/architecture/controller.md

@@ -92,9 +92,8 @@ Controllers that interact with external state find their desired state from
 the API server, then communicate directly with an external system to bring
 the current state closer in line.
 
-(There actually is a controller that horizontally scales the
-nodes in your cluster. See
-[Cluster autoscaling](/docs/tasks/administer-cluster/cluster-management/#cluster-autoscaling)).
+(There actually is a [controller](https://github.com/kubernetes/autoscaler/)
+that horizontally scales the nodes in your cluster.)
 
 The important point here is that the controller makes some change to bring about
 your desired state, and then reports current state back to your cluster's API server.

content/en/docs/concepts/architecture/nodes.md

@@ -338,5 +338,4 @@ for more information.
 * Read the [Node](https://git.k8s.io/community/contributors/design-proposals/architecture/architecture.md#the-kubernetes-node)
   section of the architecture design document.
 * Read about [taints and tolerations](/docs/concepts/scheduling-eviction/taint-and-toleration/).
-* Read about [cluster autoscaling](/docs/tasks/administer-cluster/cluster-management/#cluster-autoscaling).
 

content/en/docs/concepts/cluster-administration/_index.md

@@ -39,8 +39,6 @@ Before choosing a guide, here are some considerations:
 
 ## Managing a cluster
 
-* [Managing a cluster](/docs/tasks/administer-cluster/cluster-management/) describes several topics related to the lifecycle of a cluster: creating a new cluster, upgrading your cluster's master and worker nodes, performing node maintenance (e.g. kernel upgrades), and upgrading the Kubernetes API version of a running cluster.
-
 * Learn how to [manage nodes](/docs/concepts/architecture/nodes/).
 
 * Learn how to set up and manage the [resource quota](/docs/concepts/policy/resource-quotas/) for shared clusters.

content/en/docs/concepts/configuration/pod-priority-preemption.md

@@ -321,9 +321,7 @@ Pod may be created that fits on the same Node. In this case, the scheduler will
 schedule the higher priority Pod instead of the preemptor.
 
 This is expected behavior: the Pod with the higher priority should take the place
-of a Pod with a lower priority. Other controller actions, such as
-[cluster autoscaling](/docs/tasks/administer-cluster/cluster-management/#cluster-autoscaling),
-may eventually provide capacity to schedule the pending Pods.
+of a Pod with a lower priority.
 
 ### Higher priority Pods are preempted before lower priority pods
 

content/en/docs/tasks/administer-cluster/cluster-management.md

@@ -0,0 +1,93 @@
+---
+title: Upgrade A Cluster
+content_type: task
+---
+
+<!-- overview -->
+This page provides an overview of the steps you should follow to upgrade a
+Kubernetes cluster.
+
+The way that you upgrade a cluster depends on how you initially deployed it
+and on any subsequent changes.
+
+At a high level, the steps you perform are:
+
+- Upgrade the {{< glossary_tooltip text="control plane" term_id="control-plane" >}}
+- Upgrade the nodes in your cluster
+- Upgrade clients such as {{< glossary_tooltip text="kubectl" term_id="kubectl" >}}
+- Adjust manifests and other resources based on the API changes that accompany the
+  new Kubernetes version
+
+## {{% heading "prerequisites" %}}
+
+You must have an existing cluster. This page is about upgrading from Kubernetes
+{{< skew prevMinorVersion >}} to Kubernetes {{< skew latestVersion >}}. If your cluster
+is not currently running Kubernetes {{< skew prevMinorVersion >}} then please check
+the documentation for the version of Kubernetes that you plan to upgrade to.
+
+## Upgrade approaches
+
+### kubeadm {#upgrade-kubeadm}
+
+If your cluster was deployed using the `kubeadm` tool, refer to 
+[Upgrading kubeadm clusters](/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade/)
+for detailed information on how to upgrade the cluster.
+
+Once you have upgraded the cluster, remember to
+[install the latest version of `kubectl`](/docs/tasks/tools/install-kubectl/).
+
+### Manual deployments
+
+{{< caution >}}
+These steps do not account for third-party extensions such as network and storage
+plugins.
+{{< /caution >}}
+
+You should manually update the control plane following this sequence:
+
+- etcd (all instances)
+- kube-apiserver (all control plane hosts)
+- kube-controller-manager
+- kube-scheduler
+- cloud controller manager, if you use one
+
+At this point you should
+[install the latest version of `kubectl`](/docs/tasks/tools/install-kubectl/).
+
+For each node in your cluster, [drain](/docs/tasks/administer-cluster/safely-drain-node/)
+that node and then either replace it with a new node that uses the {{< skew latestVersion >}}
+kubelet, or upgrade the kubelet on that node and bring the node back into service.
+
+### Other deployments {#upgrade-other}
+
+Refer to the documentation for your cluster deployment tool to learn the recommended set
+up steps for maintenance.
+
+## Post-upgrade tasks
+
+### Switch your cluster's storage API version
+
+The objects that are serialized into etcd for a cluster's internal
+representation of the Kubernetes resources active in the cluster are
+written using a particular version of the API.
+
+When the supported API changes, these objects may need to be rewritten
+in the newer API. Failure to do this will eventually result in resources
+that are no longer decodable or usable by the Kubernetes API server.
+
+For each affected object, fetch it using the latest supported API and then
+write it back also using the latest supported API.
+
+### Update manifests
+
+Upgrading to a new Kubernetes version can provide new APIs.
+
+You can use `kubectl convert` command to convert manifests between different API versions.
+For example:
+
+```shell
+kubectl convert -f pod.yaml --output-version v1
+```
+
+The `kubectl` tool replaces the contents of `pod.yaml` with a manifest that sets `kind` to
+Pod (unchanged), but with a revised `apiVersion`.

content/en/docs/tasks/administer-cluster/cluster-upgrade.md

@@ -0,0 +1,29 @@
+---
+title: Enable Or Disable A Kubernetes API
+content_type: task
+---
+
+<!-- overview -->
+This page shows how to enable or disable an API version from your cluster's
+{{< glossary_tooltip text="control plane" term_id="control-plane" >}}.
+
+<!-- steps -->
+
+
+Specific API versions can be turned on or off by passing `--runtime-config=api/<version>` as a
+command line argument to the API server. The values for this argument are a comma-separated
+list of API versions. Later values override earlier values.
+
+The `runtime-config` command line argument also supports 2 special keys:
+
+- `api/all`, representing all known APIs
+- `api/legacy`, representing only legacy APIs. Legacy APIs are any APIs that have been
+   explicitly [deprecated](/docs/reference/using-api/deprecation-policy/).
+
+For example, to turning off all API versions except v1, pass `--runtime-config=api/all=false,api/v1=true`
+to the `kube-apiserver`.
+
+## {{% heading "whatsnext" %}}
+
+Read the [full documentation](/docs/reference/command-line-tools-reference/kube-apiserver/)
+for the `kube-apiserver` component.