Skip to content

fix(uptime-kuma): mark the PVC as the recurring job source - #79

Merged
PragalvaXFREZ merged 1 commit into
mainfrom
fix/uptime-kuma-recurring-job-source
Sep 6, 2026
Merged

PragalvaXFREZ merged 1 commit into
mainfrom
fix/uptime-kuma-recurring-job-source

Conversation

@PragalvaXFREZ

Copy link
Copy Markdown
Owner

What broke

After #77 the Longhorn volume never picked up recurring-job.longhorn.io/uptime-kuma-daily. Recreating the PVC did not help either. Longhorn's docs say a PVC's recurring-job labels are synced to the volume only when the PVC also carries recurring-job.longhorn.io/source: enabled. Without it the job label is inert and the volume stays in the default group.

Fix

  • Add recurring-job.longhorn.io/source: enabled to the PVC labels.
  • README corrected: two labels, synced periodically, not copied at bind time.

Argo applies the label in place. No PVC recreation, no data movement.

Validation

  • kubeconform -strict and scripts/check-docs.py pass.

After merge

kubectl -n longhorn-system get volumes.longhorn.io -o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{.metadata.labels}{"\n"}{end}' | grep uptime-kuma-daily

Longhorn only syncs recurring-job labels from a PVC to its volume when
the PVC also carries recurring-job.longhorn.io/source=enabled. The
volume was provisioned without the job label and stayed on the default
group. Add the source label and correct the README.

Signed-off-by: Pragalva Sapkota <sapkotapragalva@gmail.com>
@PragalvaXFREZ
PragalvaXFREZ merged commit daa6c38 into main Sep 6, 2026
3 checks passed
@PragalvaXFREZ
PragalvaXFREZ deleted the fix/uptime-kuma-recurring-job-source branch September 6, 2026 14:50
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.

1 participant