proposalbot
85e1a6ed92
Reviewed-by: Eotvos, Oliver <oliver.eotvos@t-systems.com> Co-authored-by: proposalbot <proposalbot@otc-service.com> Co-committed-by: proposalbot <proposalbot@otc-service.com>
35 lines
1.1 KiB
ReStructuredText
35 lines
1.1 KiB
ReStructuredText
:original_name: cce_10_0036.html
|
|
|
|
.. _cce_10_0036:
|
|
|
|
Stopping a Node
|
|
===============
|
|
|
|
Scenario
|
|
--------
|
|
|
|
After a node in the cluster is stopped, services on the node are also stopped. Before stopping a node, ensure that discontinuity of the services on the node will not result in adverse impacts.
|
|
|
|
Notes and Constraints
|
|
---------------------
|
|
|
|
- Deleting a node will lead to pod migration, which may affect services. Therefore, delete nodes during off-peak hours.
|
|
- Unexpected risks may occur during node deletion. Back up related data in advance.
|
|
- While the node is being deleted, the backend will set the node to the unschedulable state.
|
|
- Only worker nodes can be stopped.
|
|
|
|
Procedure
|
|
---------
|
|
|
|
#. Log in to the CCE console and click the cluster name to access the cluster.
|
|
|
|
#. In the navigation pane, choose **Nodes**. In the right pane, click the name of the node to be stopped.
|
|
|
|
#. In the upper right corner of the ECS details page, click **Stop** in the instance status area. In the displayed dialog box, click **Yes**.
|
|
|
|
|
|
.. figure:: /_static/images/en-us_image_0000001518062704.png
|
|
:alt: **Figure 1** ECS details page
|
|
|
|
**Figure 1** ECS details page
|