Repository navigation
[docs] Update managed apps reference for v1.7.0 - #780
Merged
Merged
Conversation
cozystack-ci
Bot
requested review from
Andrei Kvapil (kvaps),
Timofei Larkin (lllamnyp),
myasnikovdaniil and
Timur Tukaev (tym83)
as code owners
October 29, 2026 10:10
✅ Deploy Preview for cozystack ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the
 |
cozystack-ci
Bot
force-pushed
the
update-docs-v1.7.0
branch
from
October 29, 2026 11:14
73eb253 to
3de1785
Compare
myasnikovdaniil
previously approved these changes
Oct 29, 2026
Signed-off-by: cozystack-ci[bot] <274107086+cozystack-ci[bot]@users.noreply.github.com>
cozystack-ci
Bot
force-pushed
the
update-docs-v1.7.0
branch
from
October 29, 2026 11:26
3de1785 to
1bb3741
Compare
myasnikovdaniil
approved these changes
Oct 29, 2026
myasnikovdaniil
added a commit
that referenced
this pull request
Oct 30, 2026
) The v1.7 docs were cut from `next/` in #780 while several docs PRs about v1.7.0 behaviour were still open against `next/` only, so `/docs/v1.7/` and the stable `/docs/` copy miss them. This adds their content to `content/en/docs/v1.7/`, checked against the v1.7.0 tag. Every page is the source PR's `next/` file with the same `/docs/next/` rewrite that `hack/release_next.sh` does, except where noted. - #763 - #747, hand-merged after `networking.kubeovn.MASTER_NODES` because main got the `networking.encryption.enabled` row after its base - #761, with four corrections below - #762 - #766 - #764, the HTTPCache section of the upgrade guide, in both `next/` and `v1.7/` on top of the fixes from #781. I'm not carrying 764 further, this PR takes over its content. Four lines of the Proxmox page are wrong for v1.7.0 and are fixed in the v1.7 copy only. `replicas: 2` in the KubernetesNodes example is now `minReplicas: 2` and `maxReplicas: 2`, there is no `replicas` field. The CCM and CSI controller Deployments are `kubernetes-<cluster>-pccm` and `kubernetes-<cluster>-pcsi-controller`. `bundles.enabledPackages` is set on the `cozystack.cozystack-platform` Package, no ConfigMap feeds it. The CSI release depends only on the tenant Cilium release, not on the CCM, so I cut that clause. The `next/` copy in 761 needs the same fixes. The `next/` side of 763, 747, 761, 762 and 766 and the `v1.6/` side of 763, 762 and 766 stay in their own PRs, so they still merge without conflicts with this one. Nothing generated is committed, the stable `/docs/` copies are built from `v1.7/` at build time. Hugo production and preview builds, `hack/check-i18n.sh` and a link and anchor check of every changed page pass locally, with the same Hugo warnings as main.
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
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.
Automated docs update for release
v1.7.0, generated at PROMOTE time from therelease-1.7.0staging branch (fetched via FETCH_REF; the stable tagv1.7.0does not exist yet).⛔ DO NOT MERGE until
v1.7.0is published. This PR is opened before the release exists. Merging it before pull-requests-release.yaml finalize publishesv1.7.0flips the site's latest-version pointer to a version whose versioned docs and openapi.json are not on GitHub yet — every version-pin and API link for the new version 404s until the release lands. Park this PR until the GitHub release forv1.7.0is live, then merge.Opened early on purpose so the docs can be reviewed alongside the promote PR. tags.yaml::update-website-docs re-runs at tag time as a backstop and no-ops ("No changes to commit") when this already did the work.