Add doc how to check harvester status

[martindekov]

Adding documentation on how to check the status of the harvester components to the troublshooting/installation section.

The documentation is added for 1.7/1.6/1.5/1.4

Problem:

Documentation does not mention how to check harvester components status as part of the troubleshooting section

Solution:

Describe the harvester status

Related Issue(s):

harvester/harvester#9327

Test plan:

Ran locally the change to see how it looks:

Additional documentation or context

N/A

[github-actions]

Name	Link
🔨 Latest commit	8dbe0f1
😎 Deploy Preview	https://68fb489f353ebc1e3b98d8e3--harvester-preview.netlify.app

[jillian-maroket]

Review done

[jillian-maroket]

Suggested change

	## Check status of harvester components
	Before checking the status of the harvester components, acquire the kubeconfig following preferrably [the second step in the FAQ](../faq.md#how-can-i-access-the-kubeconfig-file-of-the-harvester-cluster).
	## Check the status of Harvester components
	Before checking the status of Harvester components, obtain a copy of the Harvester cluster's kubeconfig file using either of the following methods:
	- On the Harvester UI, go to the **Harvester Support** screen and then click **Download KubeConfig**.
	- Run the following commands on any of the management nodes:
	```shell
	$ sudo su
	$ cat /etc/rancher/rke2/rke2.yaml
	```

[jillian-maroket]

The FAQ content will likely be restructured or moved to other sections, so we avoid linking to that page.

[martindekov]

Jillian, since I reverted the reference I unresolved this conversation, please resolve once you double check the change

[martindekov]

Thanks Jillian, addressed your comments !

[w13915984028]

A few points to double check, thanks.

[ihcsim]

I think the step to ssh to the node is not strictly required. A user can fetch the script from anywhere on the network with something like rsync --rsync-path="sudo rsync" rancher@<vip>:/etc/rancher/rke2/rke2.yaml ./ (once <vip> is reachable). With Terraform shell provisioner, this can be used together with the readiness script below.

[martindekov]

Thanks for the input Ivan, looking at what you wrote I am starting to think that we just need to go back to referencing the section on how to get the kubeconfig, we can go around and around on how exactly kubeconfig acquisition happens, but we already have a place and the "proper explanation" should be there to be referenced. Also Jian pointed out some additional explanations I need to add, this will become guide on how to get kubeconfig as well as guide on checking cluster status which takes away from the main point which is the latter.

@jillian-maroket we initially removed the reference, it seems the explanation is becoming more complex - "how to take the kubeconfig" I will return the reference and then once we remove/move/update the kubeconfig section we can update all references to the new place.

I will leave this discussion open, but will revert the kubeconfig section reference, you can resolve the discussion if this explanation is fine when you get back online

cc @w13915984028

[ihcsim]

SGTM - Personally, I'd expect the step to fetch the kubeconfig is also scripted to work in an automated workflow, hence, my earlier comment that the whole bash script should be something user can just copy and paste into their terraform shell provisioner.

[w13915984028]

LGTM, thanks.

[ihcsim]

Thanks for working on this.

[martindekov]

Thanks for the review @dariavladykina can you please approve if those were the suggestions? I will squash btw directly commited your suggestions

[martindekov]

Since the suggestions were missed commas only, no content changes I will merge with Daria's approval. Thank you all for the reviews and suggestions!
cc @w13915984028 @ihcsim

[w13915984028]

Thanks @martindekov