[Doc][KubeRay] Add ReconcileConcurrency configuration instructions to Troubleshooting Guide

[Future-Outlier]

Why are these changes needed?

Some users may not know how to configure the ReconcileConcurrency in kuberay.

Docs link: https://anyscale-ray--55236.com.readthedocs.build/en/55236/cluster/kubernetes/troubleshooting/troubleshooting.html#how-to-configure-reconcile-concurrency-when-there-are-large-mount-of-crs

Related issue number

ray-project/kuberay#3909

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've added any new APIs to the API Reference. For example, if I added a
    method in Tune, I've added it in doc/source/tune/api/ under the
    corresponding .rst file.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[owenowenisme]

LG!

[owenowenisme]

But would it be better if we add link of this section to KubeRay autoscaler?
So users can know what to do when experiencing such scenario.
https://docs.ray.io/en/latest/cluster/kubernetes/user-guides/configuring-autoscaling.html

[Future-Outlier]

But would it be better if we add link of this section to KubeRay autoscaler? So users can know what to do when experiencing such scenario. https://docs.ray.io/en/latest/cluster/kubernetes/user-guides/configuring-autoscaling.html

great advice, let me wait for ruiean's look, thank you!

[rueian]

Mentioning concurrent workers is great, but could you also add why a user wants to change the setting more explicitly?

[Future-Outlier]

updated, thank you!

[rueian]

Hmm, the issue is still open. We'd better wait for it to be concluded if we want to reference the issue here.

[Future-Outlier]

no problem, thank you!

[angelinalg]

Suggested change

	Take [kuberay#3909](https://github.com/ray-project/kuberay/issues/3909) as an example.
	In this example, [kuberay#3909](https://github.com/ray-project/kuberay/issues/3909),

[github-actions]

This pull request has been automatically marked as stale because it has not had
any activity for 14 days. It will be closed in another 14 days if no further activity occurs.
Thank you for your contributions.

You can always ask for help on our discussion forum or Ray's public slack channel.

If you'd like to keep this open, just leave any comment, and the stale label will be removed.

[github-actions]

This pull request has been automatically closed because there has been no more activity in the 14 days
since being marked stale.

Please feel free to reopen or open a new pull request if you'd still like this to be addressed.

Again, you can always ask for help on our discussion forum or Ray's public slack channel.

Thanks again for your contribution!

[Future-Outlier]

cc @jjyao for merge, thank you!