NatLabRockies / NatLabRockies/openstudio-server-helm
Decision needed: openstorage-storage-pruner CronJob is suspended (*/10 * * * *)
Nobody has claimed this yet.
- Dominant language
- Go Template
- Stars
- 12
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Decision required
The openstorage-storage-pruner CronJob was suspended (suspend: true) during the 2026-08-24 operator sync as a precaution while the 9000-worker scale-up campaign ran. Its schedule is */10 * * * *.
Owner review needed — pick one:
- Keep suspended permanently and delete the CronJob + manifest
- Re-enable as-is (every 10 min)
- Re-enable with adjusted schedule (e.g. hourly/nightly) if the churn cost at fleet scale was the concern
Context
- Suspension was applied live on the cluster; the chart manifest state vs cluster state may now diverge — verify with
kubectl get cronjob openstorage-storage-pruner -o yamlbefore deciding. - Related follow-ups tracked in PR #113.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running kubectl get cronjob openstorage-storage-pruner -o yaml and compare the live state with the chart manifest. Read PR #113 for related follow-ups, then get the owner's decision on keeping, re-enabling, or rescheduling the CronJob. Done means the selected state is reflected consistently in the cluster and manifest, or the CronJob and manifest are removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100