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
I have read and agree to the project's Code of Conduct.
Vote on this issue by adding a 👍 reaction to the original issue initial description to help the maintainers prioritize.
Do not leave "+1" or other comments that do not add relevant information or questions.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
Description
Would like Enable-SupervisorCluster to be able to name the Supervisor cluster with a custom name. Currently it names the supervisor from the parameter -Cluster which is clearly documented as The name of the vSphere cluster. There is a parameter -mastetDNSName which is documented as "The master DNS name." Which I am not so sure I know what it means. I tried it for my purposes to no avail.
Use Case(s)
Is it a must the Supervisor Cluster is to be named the same as the vsphere cluster?
Potential Configuration
Parameter called -supervisorName....?
References
No response
The text was updated successfully, but these errors were encountered:
tenthirtyam
changed the title
Enable-SupervisorCluster - name Supervisor Cluster
Add support for Enable-SupervisorCluster to name a supervisor cluster
Sep 23, 2024
Code of Conduct
Description
Would like
Enable-SupervisorCluster
to be able to name the Supervisor cluster with a custom name. Currently it names the supervisor from the parameter-Cluster
which is clearly documented as The name of the vSphere cluster. There is a parameter-mastetDNSName
which is documented as "The master DNS name." Which I am not so sure I know what it means. I tried it for my purposes to no avail.Use Case(s)
Is it a must the Supervisor Cluster is to be named the same as the vsphere cluster?
Potential Configuration
Parameter called
-supervisorName
....?References
No response
The text was updated successfully, but these errors were encountered: