ownCloud Classic (10.x) is essentially in maintenance mode at this point. The active development and future of ownCloud is Infinite Scale (oCIS), which has its own Helm charts at https://github.com/owncloud/ocis-charts.
That raises the question: is anyone still actively using or relying on these charts in production?
Looking at the current state of this repo, most commits over the past year are automated Renovate dependency bumps - there's very little actual community-driven activity. There's an open PR from January 2024 (#77) that nobody has touched. Stars and watchers are in the single digits.
Keeping this repo alive means ongoing maintenance: staying on top of Kubernetes API deprecations, Helm tooling updates, CI pipeline upkeep, and eventually tracking ownCloud 10.x server releases for a product that isn't gaining new features. That effort adds up, especially when it's unclear if anyone is actually depending on it.
My current thinking is to archive this repository. Before doing that, I want to give the community a chance to speak up.
If you're actively using these charts, please comment. Especially if you're deploying ownCloud Classic on Kubernetes in a way that would be broken or significantly impacted by archiving. If there's enough real usage out there, that changes the calculus.
If nobody responds within a reasonable time (let's say 4-6 weeks), I'll go ahead and archive.
ownCloud Classic (10.x) is essentially in maintenance mode at this point. The active development and future of ownCloud is Infinite Scale (oCIS), which has its own Helm charts at https://github.com/owncloud/ocis-charts.
That raises the question: is anyone still actively using or relying on these charts in production?
Looking at the current state of this repo, most commits over the past year are automated Renovate dependency bumps - there's very little actual community-driven activity. There's an open PR from January 2024 (#77) that nobody has touched. Stars and watchers are in the single digits.
Keeping this repo alive means ongoing maintenance: staying on top of Kubernetes API deprecations, Helm tooling updates, CI pipeline upkeep, and eventually tracking ownCloud 10.x server releases for a product that isn't gaining new features. That effort adds up, especially when it's unclear if anyone is actually depending on it.
My current thinking is to archive this repository. Before doing that, I want to give the community a chance to speak up.
If you're actively using these charts, please comment. Especially if you're deploying ownCloud Classic on Kubernetes in a way that would be broken or significantly impacted by archiving. If there's enough real usage out there, that changes the calculus.
If nobody responds within a reasonable time (let's say 4-6 weeks), I'll go ahead and archive.