Repository navigation
docs(upgrade): give default-variant operators the HTTPCache freeze - #764
Open
myasnikovdaniil wants to merge 1 commit into
Open
myasnikovdaniil wants to merge 1 commit into
myasnikovdaniil wants to merge 1 commit into
Conversation
The v1.7 upgrade page says the HTTPCache steps of migration 58 fall to the operator on the default variant, yet its pre-upgrade checklist never mentions HTTPCache and the entry offered a check with no action. Left alone, the upgrade prunes the HTTPCache PackageSource and leaves http-cache-rd and every tenant release Ready=False for good. HTTPCache now has its own section carrying the migration's steps, so a default cluster can freeze its instances, or remove the application where none exist, before it upgrades. Assisted-by: LLM Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
myasnikovdaniil
requested review from
Andrei Kvapil (kvaps),
Timofei Larkin (lllamnyp) and
Timur Tukaev (tym83)
as code owners
October 21, 2026 10:59
✅ Deploy Preview for cozystack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Upgrade page from #757 says that on
defaultvariant the steps of migrations 54 to 59 for SeaweedFS, VM volume hotplug and HTTPCache are the operator's to take before the upgrade. SeaweedFS and hotplug got a procedure and a line in "Before you upgrade", HTTPCache got neither: checklist doesn't mention it and its entry only says to look for instances withkubectl get httpcaches.apps.cozystack.io -A.HTTPCache leaves the platform in v1.7, so the upgrade prunes its PackageSource, ArtifactGenerator and both ExternalArtifacts go with it, and
http-cache-rdwith every tenanthttp-cache-<name>release stayReady=Falsefor good. Migration 58 prevents that on other variants by freezing the PackageSource on the packages artifact the cluster already runs, or by removing the application where no instance exists.HTTPCache now has its own section next to SeaweedFS with the same steps for a
defaultcluster: instance listing, removal commands when the listing is empty, and otherwise the digest read, the pinnedcozystack-packages-http-cachecopy, PackageSource and Package patches and thecozy:tenant:admin:http-cache-frozenClusterRole. Commands are taken frommigrations/58with name variables written out and the version stamp dropped, same way the SeaweedFS section reuses migration 57. Checklistdefaultline and row 58 of the migrations table link to the new section.I ran the instance listing and the digest read on a live cluster, listing was empty there and digest read printed a
sha256:value. Freeze and removal are checked against the script only, not run on adefaultvariant cluster.Only
next/changed, it is not promoted tov1.7/yet. Checked locally: Hugo 0.164.0 build, in-page anchors, i18n checks.