Add KB about how to shutdown a Harvester cluster #68
Conversation
✅ Deploy Preview for harvester-home-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
w13915984028
force-pushed
the
doc4451
branch
3 times, most recently
from
3962be4 to
ad434a6
Compare
bk201
requested review from
FrankYang0529,
WebberHuang1118,
bk201 and
ibrokethecloud
w13915984028
force-pushed
the
doc4451
branch
11 times, most recently
from
23bf437 to
9c9d9c2
Compare
w13915984028
force-pushed
the
doc4451
branch
6 times, most recently
from
6deea38 to
63dc905
Compare
w13915984028
force-pushed
the
doc4451
branch
8 times, most recently
from
36e6663 to
41b427d
Compare
w13915984028
force-pushed
the
doc4451
branch
6 times, most recently
from
616dc39 to
3e6a1c9
Compare
|
@w13915984028 maybe I'm misunderstanding, but why is this a knowledge base article? I appreciate that it's helpful content, but realistically, this is a standard procedure that should go into the general documentation. |
@asettle Thanks. |
Signed-off-by: Jian Wang <[email protected]>
|
|
||
| :::note | ||
|
|
||
| Harvester has an `embedded rancher` deployment which is used to help the lifecycle management of Harvester itself, it is different from the independently deployed **Rancher manager** for multi-cluster management and more. |
There was a problem hiding this comment.
To keep consistency with the wording in the following text below.
| Harvester has an `embedded rancher` deployment which is used to help the lifecycle management of Harvester itself, it is different from the independently deployed **Rancher manager** for multi-cluster management and more. | |
| Harvester has an embedded `rancher` deployment which is used to help the lifecycle management of Harvester itself, it is different from the independently deployed **Rancher manager** for multi-cluster management and more. |
There was a problem hiding this comment.
As this operation also touches the external Rancher server, which is referred as Rancher manager; to distinguish from it as explicitily as possbile, the Harvester's internal rancher is called and highlighted as embedded rancher.
|
|
||
| ::: | ||
|
|
||
| The `cattle-cluster-agent-***` pod is the [direct connection between Rancher manager and Harvester cluster](https://docs.harvesterhci.io/v1.3/rancher/virtualization-management#importing-harvester-cluster), and this pod is monitored and managed by the `embedded rancher` in Harvester, scaling down this pod does not work. The `embedded rancher` will scale it up automatically. |
There was a problem hiding this comment.
I'm not sure how to handle the embedded rancher wording here. Is it about the deployment or the embedded Rancher product. i think the answer influences how embedded rancher is to be treated/adapted in the following course of the text.
|
|
||
| #### Restart the Leader Control-plane Node | ||
|
|
||
| Power on the [last shutdown node](#43-shutdown-the-last-control-plane-node) first. After about three minutes, continue the next step. |
There was a problem hiding this comment.
After about three minutes, continue the next step.
Does it make sense to use a time specification here? I think that the user's hardware is decisive in determining how long it takes. Is there not a possibility to execute a CLI command to check the status?
|
|
||
| :::note | ||
|
|
||
| If the `embedded rancher` was not scaled down before, this step can also be: |
There was a problem hiding this comment.
Based on the previous decision (see above), this should also be adjusted here.
E.g. embedded Rancher or embedded rancher, ...
|
@w13915984028 FYI: Instead of publishing the text as a KB article, I will add the information to the doc per @asettle 's feedback. I'll tag you as reviewer when the doc files are ready for review. cc: @bk201 |
|
To reviewer: This KB is still actively updating. One customer will follow this KB to relocate a production cluster. We try best to avoid any potential risks. Besides the formattings, grammers, please also help think&check more about the real operations steps, any was forgoten/missing..., thanks. |
Signed-off-by: Jian Wang <[email protected]>
w13915984028
requested review from
votdev
and removed request for
LucasSaintarbor
Issue:
harvester/harvester#4451