Merge pull request #51 from stakater/restructure-for-administrators

Restructure for administrators section
stakater · May 19, 2023 · 998fc41 · 998fc41
2 parents d653cf2 + 5c554c4
commit 998fc41
Show file tree

Hide file tree

Showing 62 changed files with 280 additions and 448 deletions.
diff --git a/content/for-administrators/autoscaling.md b/content/for-administrators/autoscaling.md
diff --git a/content/for-administrators/capacity-management.md b/content/for-administrators/capacity-management.md
@@ -0,0 +1 @@
+# Capacity Management
diff --git a/content/for-administrators/cluster-lifecycle/add-node-to-your-cluster.md b/content/for-administrators/cluster-lifecycle/add-node-to-your-cluster.md
@@ -0,0 +1 @@
+# Add a Node to your cluster
diff --git a/content/for-administrators/cluster-lifecycle/autoscale-your-cluster.md b/content/for-administrators/cluster-lifecycle/autoscale-your-cluster.md
@@ -0,0 +1 @@
+# autoscale your cluster
diff --git a/...dministrators/hibernating-your-cluster.md → ...uster-lifecycle/hibernate-your-cluster.md b/...dministrators/hibernating-your-cluster.md → ...uster-lifecycle/hibernate-your-cluster.md
@@ -1,4 +1,4 @@
-# Hibernating your Cluster
+# Hibernate your cluster
 
 For clusters running non-critical workloads, e.g. test, development or those only utilized during business hours, it is possible to schedule Cluster Hibernation to save on cloud costs, where Pay-as-you-go cloud computing (PAYG cloud computing) model is implemented.
 

diff --git a/...r-administrators/images/Saap-clusters.png → ...luster-lifecycle/images/Saap-clusters.png b/...r-administrators/images/Saap-clusters.png → ...luster-lifecycle/images/Saap-clusters.png
diff --git a/...nistrators/images/manage-powerstate-1.png → ...-lifecycle/images/manage-powerstate-1.png b/...nistrators/images/manage-powerstate-1.png → ...-lifecycle/images/manage-powerstate-1.png
diff --git a/...inistrators/images/manage-powerstate2.png → ...r-lifecycle/images/manage-powerstate2.png b/...inistrators/images/manage-powerstate2.png → ...r-lifecycle/images/manage-powerstate2.png
diff --git a/content/for-administrators/cluster-lifecycle/terminate-your-cluster.md b/content/for-administrators/cluster-lifecycle/terminate-your-cluster.md
@@ -0,0 +1 @@
+# Terminate your cluster
diff --git a/content/for-administrators/cluster-lifecycle/upgrade-your-cluster.md b/content/for-administrators/cluster-lifecycle/upgrade-your-cluster.md
@@ -0,0 +1 @@
+# Upgrade your cluster
diff --git a/content/for-administrators/cluster/.gitkeep b/content/for-administrators/cluster/.gitkeep
diff --git a/content/for-administrators/cluster/add-node.md b/content/for-administrators/cluster/add-node.md
diff --git a/content/for-administrators/cluster/images/updates-channel-1.png b/content/for-administrators/cluster/images/updates-channel-1.png
diff --git a/content/for-administrators/cluster/images/updates-channel-2.png b/content/for-administrators/cluster/images/updates-channel-2.png
diff --git a/content/for-administrators/cluster/images/updates-channel-3.png b/content/for-administrators/cluster/images/updates-channel-3.png
diff --git a/content/for-administrators/cluster/provisioning.md b/content/for-administrators/cluster/provisioning.md
diff --git a/content/for-administrators/cluster/terminate.md b/content/for-administrators/cluster/terminate.md
diff --git a/content/for-administrators/cluster/upgrade.md b/content/for-administrators/cluster/upgrade.md
diff --git a/content/for-administrators/disaster-recovery.md b/content/for-administrators/disaster-recovery.md
@@ -0,0 +1 @@
+# Disaster Recovery
diff --git a/content/for-administrators/help/faq.md b/content/for-administrators/help/faq.md
@@ -0,0 +1,6 @@
+# FAQs
+
+## Why do we reserve memory/CPU on each node?
+
+An OpenShift/Kubernetes Node consist system services that ensure the smooth running of cluster e.g. Kubelet, KubeAPIServer and other OS processes/services. These services can be starved by the workloads running on these nodes and can be starved of CPU time or can cause unexpected Out of Memory (OOM) Exceptions. In order to prevent these issues, a small chunk of resources needs to be permanently allocated to these services so they can run smoothly.
+In order to fully utilize resources. An automatic script calculates and allocates CPU/memory resources according to the node utilization. For more details see [capacity reservation docs](https://docs.openshift.com/container-platform/latest/nodes/nodes/nodes-nodes-resources-configuring.html#nodes-nodes-resources-configuring-auto_nodes-nodes-resources-configuring) for OpenShift.
diff --git a/content/for-administrators/help/troubleshooting.md b/content/for-administrators/help/troubleshooting.md
@@ -0,0 +1 @@
+# Troubleshooting
diff --git a/content/for-administrators/images/SAAP-login22.png b/content/for-administrators/images/SAAP-login22.png
diff --git a/content/for-administrators/images/Saap-login1.png b/content/for-administrators/images/Saap-login1.png
diff --git a/content/for-administrators/networking/.gitkeep b/content/for-administrators/networking/.gitkeep