Skip to content
This repository has been archived by the owner on Jun 28, 2023. It is now read-only.

Doc - Add doc for finding name of kind cluster in troubleshooting section #2612

Merged
merged 1 commit into from
Dec 2, 2021
Merged

Doc - Add doc for finding name of kind cluster in troubleshooting section #2612

merged 1 commit into from
Dec 2, 2021

Conversation

kcoriordan
Copy link
Contributor

@kcoriordan kcoriordan commented Nov 29, 2021

Signed-off-by: kcoriordan koriordan@vmware.com

What this PR does / why we need it

Add a before you begin section to the 'Troubleshoot Cluster Bootstrapping' that describes how to find the name of the kind cluster

Details for the Release Notes (PLEASE PROVIDE)


Which issue(s) this PR fixes

Fixes: #1716

Describe testing done for PR

Run hugo server as per instructions in readme

Special notes for your reviewer

Signed-off-by: kcoriordan <koriordan@vmware.com>
@kcoriordan kcoriordan requested a review from a team as a code owner November 29, 2021 16:26
@kcoriordan kcoriordan marked this pull request as draft November 29, 2021 16:26
@github-actions github-actions bot added the owner/docs Work executed by VMware documentation team label Nov 29, 2021
@kcoriordan kcoriordan changed the title WIP - Add doc for finding name of kind cluster. Doc - Add doc for finding name of kind cluster in troubleshooting section Nov 29, 2021
@kcoriordan
Copy link
Contributor Author

@karuppiah7890 pls review

@kcoriordan kcoriordan marked this pull request as ready for review November 29, 2021 16:45

The kind bootstrap cluster name and the standalone or management cluster name are not related. If there are multiple kind bootstrap clusters present, before you begin debugging, you should determine the name of the kind cluster in one or both of the following files:

* `~/.kube-tkg/tmp/`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one only has the kubeconfig but no mapping to the cluster name though, unlike data in ~/.config/tanzu/tkg/config.yaml > tkg.regions key's value

Copy link
Contributor

@karuppiah7890 karuppiah7890 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! 🚀

@vmwclabot
Copy link

@kcoriordan, your company's legal contact did not review your signed contributor license agreement within the 14 day limit. The merge can not proceed. Click here to resign the agreement.

@davidvonthenen davidvonthenen merged commit 8aa7aca into vmware-tanzu:main Dec 2, 2021
@vmwclabot
Copy link

@kcoriordan, your company's legal contact did not review your signed contributor license agreement within the 14 day limit. The merge can not proceed. Click here to resign the agreement.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
cla-rejected owner/docs Work executed by VMware documentation team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[DOCS] Docs on how to find bootstrap cluster from multiple of them in troubleshooting docs
4 participants