Coming soon — join the waitlist

GitOps-Native
Addon Upgrades

Kapstan automates the entire addon upgrade lifecycle — from changelog research to GitOps PR generation. Stop writing YAML and get back to building platform infrastructure. Zero cluster access required.

Join the waitlist for early access. No spam, ever.

github.com / your-org / infra / pull / 142

chore: upgrade argo-cd to v3.4.1

Open
kapstan-bot opened · 6 commits · 4 files changedRisk: HIGHBreaking Changes

Summary

Addonargocd
SourceCRD · argoproj/argo-cd
Upgrade pathv3.3.8 → v3.4.1
Risk levelHIGH — crosses deprecation boundary

Breaking Changes

v3.4.0ALL manifests now require Server-Side Apply. kubectl apply (client-side) is no longer supported.
v3.4.0Cluster version label format change. argocd.argoproj.io/kubernetes-version must use vMajor.Minor.Patch format.

Rollback Prerequisites

1.Back up all Argo CD CRDs and custom resources before merging.
2.Add ServerSideApply=true sync option before merging to prevent conflict errors.
apps/argocd/values.yaml +4 −2Chart.yaml +1 −1Generated by Kapstan · 0 cluster permissions used

Addon Upgrades Are Burning Engineering Hours

8-16 hrs
Average time for a breaking-change version bump
Researching, staging, testing, and writing runbooks.
1000+
Lines of changelogs to read per quarter
Missed deprecations lead directly to cluster outages.
12+
Addons in a typical production cluster
Each with its own upgrade cadence and quirks.

The Manual Way vs. The Kapstan Way

Same outcome. One route involves 8-16 hours of toil.

The Manual Way
  1. 1Notice version drift — usually from a Slack alert or a failed sync.
  2. 2Read 6 minor-version changelogs end-to-end.
  3. 3Cross-reference deprecated APIs against your current values.yaml.
  4. 4Manually edit values.yaml and any dependent manifests.
  5. 5Write rollback runbooks. Hope they're complete.
  6. 6Open a PR. Reviewers have no structured context to approve against.
The Kapstan Way
  • 1Review Kapstan's context-rich PR and click Merge. Your CI/CD and Argo CD handle the rest.

    • Eliminate YAML toil. Your engineers stop writing manifests and start approving architecture.

    Three Steps to Upgrade Confidence

    01

    Detect

    Kapstan continuously maps your GitOps repository against the latest CNCF releases. No cluster agents required.

    02

    Architect

    Our deterministic AI writes the YAML diffs, maps breaking changes, and generates the rollback plan natively in Git.

    03

    Deliver

    You get a pristine Pull Request ready for review. You merge; your CI/CD and Argo CD take over.