docs(networking): drop HTTPCache and hold back the Cloudflare Tunnel page for 1.7

[myasnikovdaniil]

make release-next RELEASE_TAG=v1.7.0 copies next/ into v1.7/ as is, and make update-all then regenerates reference pages from 1.7 README files. Two things in next/ break that.

HTTPCache was removed from the catalog in cozystack/cozystack#4200, so packages/apps/http-cache doesn't exist at 1.7. The NETWORKING list still names it, hack/update_apps.sh gets 404 on its README and exits 1, so update-all stops right after release-next and no docs PR is opened. First commit drops it from the list, deletes the page and its stub and cleans remaining mentions in next/ (ApplicationDefinition examples now use VMInstance, NGINX and IP2Location cards are gone because they described only HTTPCache). Older version directories keep their HTTPCache pages, those releases ship it. content/en/_index.md still lists HTTP caching services, I left it for a separate change.

Cloudflare Tunnel page documents the package from cozystack/cozystack#3858, still a draft and not in 1.7. Second commit removes the page, its card in licenses and the one link to it from the Gateway API page. It is one commit, so git revert of it brings everything back when the package ships.

I replayed the promotion sequence on a copy of the tree (release-next, then update-all with FETCH_REF=v1.7.0-rc.1). On main it fails with 404 for the http-cache README, with this branch it completes, and Hugo 0.164.0 production build of the promoted v1.7/ is clean, no links to the removed pages. Preview build and i18n checks pass too.

#728 edits the line right below NETWORKING, so it conflicts with this PR in any order. Whichever lands second needs one-line fix: keep its block and drop http-cache from NETWORKING.

[netlify]

✅ Deploy Preview for cozystack ready!

Name	Link
🔨 Latest commit	439a646
🔍 Latest deploy log	https://app.netlify.com/projects/cozystack/deploys/6ad6f3dc0b60aa17fd328850
😎 Deploy Preview	https://deploy-preview-755--cozystack.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 95045dc1-7d9c-4db0-83c8-2c44882ee261

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[IvanHunters]

LGTM.

Verified the removal is complete and build-safe on the next/ tree: no ref links to the deleted pages remain (the leftover http-cache/cloudflare-tunnel references are all in the frozen v0/v1.0–v1.2 snapshots, where the pages still ship), the deleted http-cache.md alias paths are not linked from next/, the cozystack-api CRD table is consistent after dropping httpcaches, and the application-definitions.md HTTPCache→VMInstance example migration is accurate (ToLower("VMInstance") == "vminstance" matches singular but not the vm-instance CRD name — same divergence the old example showed).

One non-blocking note:

• content/en/docs/next/networking/gateway-api.md:469 still reads "That is the hole the Cloudflare Tunnel package closes with its own ownership layer...". The ref link to the page was removed from this file, but this prose mention stayed. For 1.7, where the package is intentionally held back, this asserts a mitigation that does not ship. Folding the clause removal into the second commit would keep the page accurate and keep the git revert-when-it-ships story whole. Not a blocker.