Skip to content

fix(nextcloud): add explicit group/kind to HTTPRoute backendRefs to prevent Argo CD drift#868

Merged
varet80 merged 1 commit into
nextcloud:mainfrom
somaz94:fix/httproute-argo-drift
Jul 14, 2026
Merged

fix(nextcloud): add explicit group/kind to HTTPRoute backendRefs to prevent Argo CD drift#868
varet80 merged 1 commit into
nextcloud:mainfrom
somaz94:fix/httproute-argo-drift

Conversation

@somaz94

@somaz94 somaz94 commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Description of the change

The HTTPRoute template rendered backendRefs with only name, port, and
weight. The Gateway API defaults group: "" and kind: Service server-side,
so the live object always contains two fields the Helm-rendered manifest omits.
Argo CD has no way to know these CRD defaults, so it reports the app OutOfSync
and re-syncs in a loop.

This renders group: "" and kind: Service explicitly so the desired manifest
matches the reconciled live state. No behavior change, no new values.

Benefits

  • Deterministic HTTPRoute rendering, compatible with GitOps / Argo CD
  • No more continuous drift / re-sync loops on the generated HTTPRoute
  • Users no longer need a custom ignoreDifferences rule on .spec.rules[].backendRefs

Possible drawbacks

None. The two added fields are the effective API defaults the chart already relied on.

Applicable issues

Additional information

Validated locally against main:

  • ct lint (the CI gate) passes; chart version bump detected (9.2.0 -> 9.2.1)
  • helm lint --set httpRoute.enabled=true passes
  • helm template rendered with httpRoute disabled (no output), a default rule, and a custom filter+timeouts rule; group/kind present in every enabled case

Checklist

  • I have read the CONTRIBUTING.md doc.
  • DCO has been signed off on the commit.
  • Chart version bumped in Chart.yaml according to semver.
  • (optional) Parameters are documented in the README.md (no new parameters)

somaz94 added a commit to somaz94/somaz94 that referenced this pull request Jul 3, 2026
@somaz94 somaz94 marked this pull request as ready for review July 10, 2026 02:54
@wrenix wrenix enabled auto-merge (squash) July 10, 2026 05:24
…revent Argo CD drift

Signed-off-by: somaz <genius5711@gmail.com>
auto-merge was automatically disabled July 13, 2026 01:56

Head branch was pushed to by a user without write access

@somaz94 somaz94 force-pushed the fix/httproute-argo-drift branch from cd4076b to e210b43 Compare July 13, 2026 01:56
@varet80 varet80 enabled auto-merge July 14, 2026 18:41
@varet80 varet80 merged commit edb4fd6 into nextcloud:main Jul 14, 2026
12 checks passed
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.

HTTPRoute manifests generated by Gateway API integration cause Argo CD drift detection

3 participants