Removing Manage Nodes from Architecture doc

Author: mburke5678

modules/node-management.adoc

@@ -122,100 +122,3 @@ Events:                    <none>
 <2> The user defined configuration.
 <3> The Machine Config Pool selector to apply the KubeletConfig to.
 
-[[modifying-nodes]]
-== Modifying Nodes
-
-{product-title} uses a KubeletConfig Custom Resource to manage the
-configuration of nodes. By creating an instance of a KubeletConfig, a managed
-MachineConfig is created to override setting on the node. 
-
-[NOTE]
-====
-*Logging into remote machines for the purpose of changing their configuration is not supported.*
-====
-
-To make configuration changes to a MachinePool, you need to create a KubeletConfig instance. The Machine Config Controller watches for 
-KubeletConfigs and applies the configuration.
-
-.Sample configuration for a *max-pods* KubeletConfig
-----
-apiVersion: machineconfiguration.openshift.io/v1
-kind: KubeletConfig
-metadata:
-  name: set-max-pods <1>
-spec:
-  machineConfigPoolSelector:
-    matchLabels: <2>
-      custom-kubelet: small-pods
-  kubeletConfig: <3>
-    maxPods: 100
-----
-
-<1> The name of the KubeletConfig.
-<2> The MachineConfigPool selector to apply the KubeletConfig to.
-<3> https://github.com/kubernetes/kubernetes/blob/release-1.11/pkg/kubelet/apis/kubeletconfig/v1beta1/types.go#L45[KubeletConfig Options]
-
-Most https://github.com/kubernetes/kubernetes/blob/release-1.11/pkg/kubelet/apis/kubeletconfig/v1beta1/types.go#L45[KubeletConfig Options]  may be set by the user. The following options are not allowed to be overwritten:
-
-* CgroupDriver
-* ClusterDNS
-* ClusterDomain
-* RuntimeRequestTimeout
-* StaticPodPath
-
-[[admin-guide-max-pods-per-node]]
-=== Setting maximum pods per node
-
-////
-The following section is included in the Scaling and Performance Guide.
-////
-// tag::admin_guide_manage_nodes[]
-
-In the KubeletConfig, two parameters control the maximum number of pods that
-can be scheduled to a node: `podsPerCore` and `maxPods`. When both options
-are in use, the lower of the two limits the number of pods on a node.
-Exceeding these values can result in:
-
-* Increased CPU utilization on both {product-title} and Docker.
-* Slow pod scheduling.
-* Potential out-of-memory scenarios (depends on the amount of memory in the node).
-* Exhausting the pool of IP addresses.
-* Resource overcommitting, leading to poor user application performance.
-
-[NOTE]
-====
-In Kubernetes, a pod that is holding a single container actually uses two
-containers. The second container is used to set up networking prior to the
-actual container starting. Therefore, a system running 10 pods will actually
-have 20 containers running.
-====
-
-`podsPerCore` sets the number of pods the node can run based on the number of
-processor cores on the node. For example, if `podsPerCore` is set to `10` on
-a node with 4 processor cores, the maximum number of pods allowed on the node
-will be 40.
-
-----
-spec:
-  kubeletConfig:
-    podsPerCore: 100
-----
-
-[NOTE]
-====
-Setting `podsPerCore` to 0 disables this limit.
-====
-
-`maxPods` sets the number of pods the node can run to a fixed value, regardless
-of the properties of the node.
-
-----
-spec:
-  kubeletConfig:
-    maxPods: 250
-----
-
-Using the above example, the default value for `podsPerCore` is `10` and the
-default value for `maxPods` is `250`. This means that unless the node has 25
-cores or more, by default, `podsPerCore` will be the limiting factor.
-// end::admin_guide_manage_nodes[]