Skip to content

Conversation

@Kelketek
Copy link
Contributor

@Kelketek Kelketek commented Aug 5, 2025

Description

This Merge request updates the URL in the High-Availability documentation to point to the stable branch, just as the getting started documentation has. Using the master version of the installation manifests by mistake can cause hours of wasted time on behalf of the operator. Ask me how I know. :)

Recommended cherry-picks

Whatever version of the docs is currently published (stable?) should have this commit cherry-picked.

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).
  • The title of the PR conforms to the Title of the PR
  • 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.
  • 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).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

@Kelketek Kelketek requested review from a team as code owners August 5, 2025 19:05
@bunnyshell
Copy link

bunnyshell bot commented Aug 5, 2025

❌ Preview Environment deleted from Bunnyshell

Available commands (reply to this comment):

  • 🚀 /bns:deploy to deploy the environment

@Kelketek Kelketek force-pushed the fox/update-ha-manifest-url branch from 8e8a4ab to cc9a955 Compare August 5, 2025 19:07
@reggie-k reggie-k merged commit 2cfc70a into argoproj:master Sep 8, 2025
24 checks passed
@reggie-k
Copy link
Member

reggie-k commented Sep 8, 2025

Thanks for the PR @Kelketek ! Can you create cherry-pick PRs for release-3.1, release-3.0 and release-2.14 branches? We used to use cherry-pick bot for this tasks before, but it is not available anymore.

@Kelketek
Copy link
Contributor Author

Kelketek commented Sep 8, 2025

@reggie-k Done. Please find #24454 , #24455 , and #24456

@Kelketek
Copy link
Contributor Author

Kelketek commented Sep 8, 2025

@reggie-k All three have failed CI. Not sure if you need me to do anything there, since I wouldn't expect a link in the docs to cause a problem.

@reggie-k
Copy link
Member

reggie-k commented Sep 9, 2025

@Kelketek thanks! I merged all of them. The error is indeed unrelated to the change and is a common issue with PR against release branches.

Mangaal pushed a commit to Mangaal/argo-cd that referenced this pull request Sep 10, 2025
LogicalShark pushed a commit to LogicalShark/argo-cd that referenced this pull request Sep 10, 2025
Hapshanko pushed a commit to Hapshanko/argo-cd that referenced this pull request Sep 12, 2025
downfa11 pushed a commit to downfa11/argo-cd that referenced this pull request Sep 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants