RHDEVDOCS-7943: Document Argo CD continue parameter sync failure

[npawarr]

Summary

• Add a new OpenShift GitOps troubleshooting topic for Argo CD application sync failures that report continue parameter is too old.
• Document tuning ARGOCD_CLUSTER_CACHE_LIST_PAGE_SIZE and ARGOCD_CLUSTER_CACHE_LIST_PAGE_BUFFER_SIZE through the ArgoCD CR spec.controller.env field.
• Update the GitOps topic map and reference KCS 7138154.

Jira

https://redhat.atlassian.net/browse/RHDEVDOCS-7943

Test plan

• Verify the new topic builds in the Netlify preview
• Confirm the troubleshooting topic appears under Troubleshooting issues
• Review YAML example and oc verification commands for accuracy
• SME review against KCS 7138154 resolution guidance

[openshift-ci-robot]

@npawarr: This pull request references RHDEVDOCS-7943 which is a valid jira issue.

Details

In response to this:

Summary

• Add a new OpenShift GitOps troubleshooting topic for Argo CD application sync failures that report continue parameter is too old.
• Document tuning ARGOCD_CLUSTER_CACHE_LIST_PAGE_SIZE and ARGOCD_CLUSTER_CACHE_LIST_PAGE_BUFFER_SIZE through the ArgoCD CR spec.controller.env field.
• Update the GitOps topic map and reference KCS 7138154.

Jira

https://redhat.atlassian.net/browse/RHDEVDOCS-7943

Test plan

• Verify the new topic builds in the Netlify preview
• Confirm the troubleshooting topic appears under Troubleshooting issues
• Review YAML example and oc verification commands for accuracy
• SME review against KCS 7138154 resolution guidance

Made with Cursor

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

Hi @npawarr. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.