Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cluster-id with just VC-IP on multi clustered VC is error prone #143

Open
rpanduranga opened this issue Jan 18, 2022 · 1 comment
Open
Milestone

Comments

@rpanduranga
Copy link

Issue/Feature Description:
cluster-id with just VC-IP on multi clustered VC is error prone

cluster-id: The unique cluster identifier. Each Kubernetes cluster must contain a unique cluster-id set in the configuration file. The cluster ID cannot not exceed 64 characters.

What type of Issue/Feature is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:

/kind bug fix

Why this fix/ feature is needed(give scenarios or use cases):
Currently the vsphere-config-secret is created with the cluster-id as VC-IP
here is the decoded output of the secret

[Global]
cluster-id = "VCIP"

[VirtualCenter "VCIP"]
insecure-flag = "true"
user = "[email protected]"
password = "Admin!23"
datacenters = "VSAN-DC"

On the multi clustered VC, if the two or more clusters are configured with the same cluster-id then it is an error prone for the
CNS analytics

How to reproduce, in case of a bug:
Configure a setup with multi cluster and deploy multiple k8s cluster in it

Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)
https://docs.vmware.com/en/VMware-vSphere-Container-Storage-Plug-in/2.0/vmware-vsphere-csp-getting-started/GUID-BFF39F1D-F70A-4360-ABC9-85BDAFBE8864.html

@asifdxtreme asifdxtreme added this to the Sprint-6 milestone Feb 2, 2022
@asifdxtreme
Copy link
Collaborator

/cc @jvrahav

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@asifdxtreme @rpanduranga and others