Troubleshooting docs update: Cluster sub command not available

[epacke]

Signed-off-by: Patrik Jonsson patrik.jonsson@gmail.com

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).

[codecov]

Codecov Report

Merging #5834 (af7b6b9) into master (ccfa058) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #5834   +/-   ##
=======================================
  Coverage   41.01%   41.01%           
=======================================
  Files         146      146           
  Lines       19630    19630           
=======================================
  Hits         8052     8052           
  Misses      10464    10464           
  Partials     1114     1114           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ccfa058...af7b6b9. Read the comment docs.

[epacke]

First of all, hats off for an excellent application! <3

On v1.8.7+eb3d1fb when following the Operator troubleshooting steps for problems with manually added cluster credentials.

Executed in the application controller container:

argocd-util cluster kubeconfig https://rancher.xip.io /tmp/kubeconfig --namespace argocd
Error: unknown command "cluster" for "argocd-util"
Run 'argocd-util --help' for usage.
unknown command "cluster" for "argocd-util

Removing "cluster" from the command makes it work like a charm.

[kshamajain99]

This command is part of recent change #5690. It will be available in v2.0.

[kshamajain99]

If you are using argocd v1.8 then please use corresponding document version https://argo-cd.readthedocs.io/en/release-1.8/operator-manual/troubleshooting/

[kshamajain99]

Hi @epacke,
Argo CD provides a way for you to select a particular version of docs that you are using (for more details refer PR). Here is the link to v1.8 Argo CD docs which has the old Argo CD util command argocd-util kubeconfig https://argo-cd.readthedocs.io/en/release-1.8/operator-manual/troubleshooting/.

argocd-util cluster <sub-commands> was added recently.

Thank you for submitting a PR. I will close this one.