vPotato/virtuallypotato
1
0
Fork 0
mirror of https://github.com/jbowdre/virtuallypotato.git synced 2024-12-22 11:12:18 +00:00
Code Issues Projects Releases Packages Wiki Activity

add warning

Browse source
This commit is contained in:
John Bowdre 2022-07-25 16:01:26 -05:00
parent 5ed9ab56a4
commit 7682c38f7d
1 changed files with 5 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
content/posts/removing-recreating-vcls-vms/index.md
View file

@ -1,7 +1,7 @@
---
title: "Removing and Recreating vCLS VMs" # Title of the blog post.
date: 2022-07-24
# lastmod: 2022-07-23T16:25:05-05:00 # Date when last modified
lastmod: 2022-07-25 # Date when last modified
description: "How to remove and (optionally) recreate the vSphere Clustering Services VMs" # Description used for search engine.
featured: false # Sets if post is a featured post, making appear on the home page side bar.
draft: false # Sets whether to render this page. Draft of true will not be rendered.
@ -32,6 +32,10 @@ That's very cool, particularly in large continent-spanning environments or those
Fortunately there's a somewhat-hidden way to disable (and re-enable) vCLS on a per-cluster basis, and it's easy to do once you know the trick. This can help if you want to permanently disable vCLS (like in a lab environment) or if you just need to turn it off and on again[^off-and-on] to clean up and redeploy uncooperative agent VMs.
{{% notice warning "Proceed at your own risk" %}}
Disabling vCLS will break DRS, and could have other unintended side effects. Don't do this in prod if you can avoid it.
{{% /notice %}}
[^off-and-on]: ![](off-and-on.gif)
### Find the cluster's domain ID