You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: cloud_experts_tutorials/cloud-experts-deploying-application/cloud-experts-deploying-application-prerequisites.adoc
-10Lines changed: 0 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -13,22 +13,12 @@ toc::[]
13
13
14
14
. A Provisioned ROSA cluster
15
15
+
16
-
<<<<<<< HEAD
17
16
ifdef::openshift-rosa-hcp[]
18
17
This lab assumes you have access to a successfully provisioned a ROSA cluster. If you have not yet created a ROSA cluster, see xref:../../rosa_hcp/rosa-hcp-quickstart-guide.adoc#rosa-getting-started-environment-setup_rosa-hcp-quickstart-guide[ROSA with HCP quick start guide] for more information.
19
18
endif::openshift-rosa-hcp[]
20
19
ifdef::openshift-rosa[]
21
20
This lab assumes you have access to a successfully provisioned a ROSA cluster. If you have not yet created a ROSA cluster, see xref:../../rosa_getting_started/rosa-quickstart-guide-ui.adoc#rosa-getting-started-environment-setup_rosa-quickstart-guide-ui[ROSA quick start guide] for more information.
22
21
endif::openshift-rosa[]
23
-
=======
24
-
This lab assumes you have access to a successfully provisioned a ROSA cluster. If you have not yet created a ROSA cluster, see
25
-
ifdef::openshift-rosa-hcp[]
26
-
link:https://docs.openshift.com/rosa/rosa_getting_started/rosa-quickstart-guide-ui.html#rosa-getting-started-prerequisites_rosa-quickstart-guide-ui[Red{nbsp}Hat OpenShift Service on AWS quick start guide] for more information.
27
-
endif::openshift-rosa-hcp[]
28
-
ifndef::openshift-rosa-hcp[]
29
-
xref:../../rosa_getting_started/rosa-quickstart-guide-ui.adoc#rosa-getting-started-prerequisites_rosa-quickstart-guide-ui[Red{nbsp}Hat OpenShift Service on AWS quick start guide] for more information.
30
-
endif::openshift-rosa-hcp[]
31
-
>>>>>>> 7f6bdc8cdc (Updated the HCP migration to include the ROSA Tutorals and Learning sections)
* xref:../nodes/nodes/nodes-nodes-managing-max-pods.adoc#nodes-nodes-managing-max-pods-proc_nodes-nodes-managing-max-pods[Configure the number of pods that can run on a node] based on the number of processor cores on the node, a hard limit, or both.
55
53
* Reboot a node gracefully using xref:../nodes/nodes/nodes-nodes-rebooting.adoc#nodes-nodes-rebooting-affinity_nodes-nodes-rebooting[pod anti-affinity].
56
54
* xref:../nodes/nodes/nodes-nodes-working.adoc#deleting-nodes[Delete a node from a cluster] by scaling down the cluster using a compute machine set. To delete a node from a bare-metal cluster, you must first drain all pods on the node and then manually delete the node.
{product-title} allows you to do more than just access and manage nodes; as an administrator, you can perform the following tasks on nodes to make the cluster more efficient, application-friendly, and to provide a better environment for your developers.
63
61
64
-
* Manage node-level tuning for high-performance applications that require some level of kernel tuning by
xref:../nodes/nodes/nodes-node-tuning-operator.adoc#nodes-node-tuning-operator[using the Node Tuning Operator].
67
-
* xref:../nodes/jobs/nodes-pods-daemonsets.adoc#nodes-pods-daemonsets[Run background tasks on nodes automatically with daemon sets]. You can create and use daemon sets to create shared storage, run a logging pod on every node, or deploy a monitoring agent on all nodes.
* Manage node-level tuning for high-performance applications that require some level of kernel tuning by xref:../nodes/nodes/nodes-node-tuning-operator.adoc#nodes-node-tuning-operator[using the Node Tuning Operator].
63
+
ifndef::openshift-rosa,openshift-dedicated[]
70
64
* Enable TLS security profiles on the node to protect communication between the kubelet and the Kubernetes API server.
65
+
endif::openshift-rosa,openshift-dedicated[]
66
+
* xref:../nodes/jobs/nodes-pods-daemonsets.adoc#nodes-pods-daemonsets[Run background tasks on nodes automatically with daemon sets]. You can create and use daemon sets to create shared storage, run a logging pod on every node, or deploy a monitoring agent on all nodes.
67
+
ifndef::openshift-rosa,openshift-dedicated[]
71
68
* xref:../nodes/nodes/nodes-nodes-garbage-collection.adoc#nodes-nodes-garbage-collection[Free node resources using garbage collection]. You can ensure that your nodes are running efficiently by removing terminated containers and the images not referenced by any running pods.
72
69
* xref:../nodes/nodes/nodes-nodes-managing.adoc#nodes-nodes-kernel-arguments_nodes-nodes-managing[Add kernel arguments to a set of nodes].
73
70
* Configure an {product-title} cluster to have worker nodes at the network edge (remote worker nodes). For information on the challenges of having remote worker nodes in an {product-title} cluster and some recommended approaches for managing pods on a remote worker node, see xref:../nodes/edge/nodes-edge-remote-workers.adoc#nodes-edge-remote-workers[Using remote worker nodes at the network edge].
* link:https://docs.openshift.com/rosa/nodes/jobs/nodes-pods-daemonsets.html#nodes-pods-daemonsets[Run background tasks on nodes automatically with daemon sets]. You can create and use daemon sets to create shared storage, run a logging pod on every node, or deploy a monitoring agent on all nodes.
77
-
endif::openshift-rosa-hcp,openshift-rosa[]
71
+
endif::openshift-rosa,openshift-dedicated[]
78
72
79
73
[id="pods-overview"]
80
74
== About pods
@@ -86,50 +80,36 @@ A pod is one or more containers deployed together on a node. As a cluster admini
86
80
87
81
As an administrator, you can get information about pods in a project through the following tasks:
88
82
89
-
ifdef::openshift-rosa-hcp[]
90
-
* link:https://docs.openshift.com/rosa/nodes/pods/nodes-pods-viewing.html#nodes-pods-viewing-project_nodes-pods-viewing[List pods associated with a project], including information such as the number of replicas and restarts, current status, and age.
91
-
* link:https://docs.openshift.com/rosa/nodes/pods/nodes-pods-viewing.html#nodes-pods-viewing-usage_nodes-pods-viewing[View pod usage statistics] such as CPU, memory, and storage consumption.
92
-
ifndef::openshift-rosa-hcp[]
93
83
* xref:../nodes/pods/nodes-pods-viewing.adoc#nodes-pods-viewing-project_nodes-pods-viewing[List pods associated with a project], including information such as the number of replicas and restarts, current status, and age.
94
84
* xref:../nodes/pods/nodes-pods-viewing.adoc#nodes-pods-viewing-usage_nodes-pods-viewing[View pod usage statistics] such as CPU, memory, and storage consumption.
95
-
endif::openshift-rosa-hcp[]
96
85
97
86
[discrete]
98
87
=== Management operations
99
88
100
89
The following list of tasks provides an overview of how an administrator can manage pods in an {product-title} cluster.
101
90
102
91
* Control scheduling of pods using the advanced scheduling features available in {product-title}:
103
-
ifdef::openshift-rosa-hcp[]
104
-
** Node-to-pod binding rules such as link:https://docs.openshift.com/rosa/nodes/scheduling/nodes-scheduler-pod-affinity.html#nodes-scheduler-pod-affinity-example-affinity_nodes-scheduler-pod-affinity[pod affinity], link:https://docs.openshift.com/rosa/nodes/scheduling/nodes-scheduler-node-affinity.html#nodes-scheduler-node-affinity[node affinity], and link:https://docs.openshift.com/rosa/nodes/scheduling/nodes-scheduler-pod-affinity.html#nodes-scheduler-pod-anti-affinity-configuring_nodes-scheduler-pod-affinity[anti-affinity].
105
-
** link:https://docs.openshift.com/rosa/nodes/scheduling/nodes-scheduler-node-selectors.html#nodes-scheduler-node-selectors[Node labels and selectors].
* link:https://docs.openshift.com/rosa/nodes/pods/nodes-pods-configuring.html#nodes-pods-configuring-restart_nodes-pods-configuring[Configure how pods behave after a restart using pod controllers and restart policies].
108
-
* link:https://docs.openshift.com/rosa/nodes/pods/nodes-pods-configuring.html#nodes-pods-configuring-bandwidth_nodes-pods-configuring[Limit both egress and ingress traffic on a pod].
109
-
* link:https://docs.openshift.com/rosa/nodes/containers/nodes-containers-volumes.html#nodes-containers-volumes[Add and remove volumes to and from any object that has a pod template]. A volume is a mounted file system available to all the containers in a pod. Container storage is ephemeral; you can use volumes to persist container data.
110
-
endif::openshift-rosa-hcp[]
111
-
ifndef::openshift-rosa-hcp[]
112
92
** Node-to-pod binding rules such as xref:../nodes/scheduling/nodes-scheduler-pod-affinity.adoc#nodes-scheduler-pod-affinity-example-affinity_nodes-scheduler-pod-affinity[pod affinity], xref:../nodes/scheduling/nodes-scheduler-node-affinity.adoc#nodes-scheduler-node-affinity[node affinity], and xref:../nodes/scheduling/nodes-scheduler-pod-affinity.adoc#nodes-scheduler-pod-anti-affinity-configuring_nodes-scheduler-pod-affinity[anti-affinity].
113
93
** xref:../nodes/scheduling/nodes-scheduler-node-selectors.adoc#nodes-scheduler-node-selectors[Node labels and selectors].
* xref:../nodes/scheduling/descheduler/index.adoc#nodes-descheduler-about[Configure the descheduler to evict pods] based on specific strategies so that the scheduler reschedules the pods to more appropriate nodes.
* xref:../nodes/pods/nodes-pods-configuring.adoc#nodes-pods-configuring-restart_nodes-pods-configuring[Configure how pods behave after a restart using pod controllers and restart policies].
123
104
* xref:../nodes/pods/nodes-pods-configuring.adoc#nodes-pods-configuring-bandwidth_nodes-pods-configuring[Limit both egress and ingress traffic on a pod].
124
105
* xref:../nodes/containers/nodes-containers-volumes.adoc#nodes-containers-volumes[Add and remove volumes to and from any object that has a pod template]. A volume is a mounted file system available to all the containers in a pod. Container storage is ephemeral; you can use volumes to persist container data.
125
-
endif::openshift-rosa-hcp[]
126
106
127
107
[discrete]
128
108
=== Enhancement operations
129
109
130
110
You can work with pods more easily and efficiently with the help of various tools and features available in {product-title}. The following operations involve using those tools and features to better manage pods.
@@ -152,17 +132,12 @@ As a developer, use a vertical pod autoscaler to ensure your pods stay up during
152
132
|Administrator
153
133
|Some applications need sensitive information, such as passwords and usernames. You can use the `Secret` object to provide such information to an application pod.
* Secrets: Some applications need sensitive information, such as passwords and usernames. An administrator can use the `Secret` object to provide sensitive data to pods
159
-
ifdef::openshift-rosa-hcp[]
160
-
link:https://docs.openshift.com/rosa/nodes/pods/nodes-pods-secrets.html#nodes-pods-secrets[using the `Secret` object].
161
-
endif::openshift-rosa-hcp[]
162
-
ifndef::openshift-rosa-hcp[]
163
-
xref:../nodes/pods/nodes-pods-secrets.adoc#nodes-pods-secrets[using the `Secret` object].
* Secrets: Some applications need sensitive information, such as passwords and usernames. An administrator can use the `Secret` object to provide sensitive data to pods xref:../nodes/pods/nodes-pods-secrets.adoc#nodes-pods-secrets[using the `Secret` object].
140
+
endif::openshift-rosa,openshift-dedicated[]
166
141
167
142
[id="containers-overview"]
168
143
== About containers
@@ -172,32 +147,18 @@ A container is the basic unit of an {product-title} application, which comprises
172
147
Linux container technologies are lightweight mechanisms for isolating running processes and limiting access to only designated resources.
173
148
As an administrator, You can perform various tasks on a Linux container, such as:
174
149
175
-
ifdef::openshift-rosa-hcp[]
176
-
* link:https://docs.openshift.com/rosa/nodes/containers/nodes-containers-copying-files.html#nodes-containers-copying-files[Copy files to and from a container].
177
-
* link:https://docs.openshift.com/rosa/nodes/containers/nodes-containers-downward-api.html#nodes-containers-downward-api[Allow containers to consume API objects].
178
-
* link:https://docs.openshift.com/rosa/nodes/containers/nodes-containers-remote-commands.html#nodes-containers-remote-commands[Execute remote commands in a container].
179
-
* link:https://docs.openshift.com/rosa/nodes/containers/nodes-containers-port-forwarding.html#nodes-containers-port-forwarding[Use port forwarding to access applications in a container].
180
-
endif::openshift-rosa-hcp[]
181
-
ifndef::openshift-rosa-hcp[]
182
150
* xref:../nodes/containers/nodes-containers-copying-files.adoc#nodes-containers-copying-files[Copy files to and from a container].
183
151
* xref:../nodes/containers/nodes-containers-downward-api.adoc#nodes-containers-downward-api[Allow containers to consume API objects].
184
152
* xref:../nodes/containers/nodes-containers-remote-commands.adoc#nodes-containers-remote-commands[Execute remote commands in a container].
185
153
* xref:../nodes/containers/nodes-containers-port-forwarding.adoc#nodes-containers-port-forwarding[Use port forwarding to access applications in a container].
186
-
endif::openshift-rosa-hcp[]
187
154
188
-
{product-title} provides specialized containers called
. Init containers run before application containers and can contain utilities or setup scripts not present in an application image. You can use an Init container to perform tasks before the rest of a pod is deployed.
155
+
{product-title} provides specialized containers called xref:../nodes/containers/nodes-containers-init.adoc#nodes-containers-init[Init containers]. Init containers run before application containers and can contain utilities or setup scripts not present in an application image. You can use an Init container to perform tasks before the rest of a pod is deployed.
196
156
197
157
Apart from performing specific tasks on nodes, pods, and containers, you can work with the overall {product-title} cluster to keep the cluster efficient and the application pods highly available.
198
158
159
+
199
160
//cannot create the required namespace for these operators
The Vertical Pod Autoscaler (VPA) can automatically review the historic and current CPU and memory resources for containers in pods and can update the resource limits and requests based on the usage values it learns.
218
179
+
219
180
For more information, see xref:../nodes/pods/nodes-pods-vertical-autoscaler.adoc#nodes-pods-vpa[Automatically adjust pod resource levels with the vertical pod autoscaler].
Implemented as a Kubernetes API resource and a controller. You can use the HPA to specify the minimum and maximum number of pods that you want to run. You can also specify the CPU or memory utilization that your pods should target. The HPA scales out and scales in pods when a given CPU or memory threshold is crossed.
0 commit comments