Repository navigation
docs(upgrade): carry the Kubernetes app's breaking changes to the v1.7 upgrade page - #803
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 Kubernetes app README is losing its Breaking Changes section, and the v1.7 upgrade page is where an operator coming from v1.6 reads what the upgrade changes for tenant clusters. Most of that section is already there; this adds what is not. Worker pools: what migration 56 carries into each adopted pool (the cluster's talos values, the effective health-check settings, maxNodeProvisionTime), the 50% remediation default a new pool takes, that WorkloadsReady on the Kubernetes resource now covers the control plane only, and that pools are deleted before the cluster. A new subsection says where a pool's Talos image, installer and registry mirrors are set, that the Kubernetes resource does not read those talos keys, and that the platform registries value never reached Talos workers and goes away with its patch-containerd Secret in v1.7.1. Kamaji: the admission plugin enum, and repeated feature-gate spellings or kube emulated versions now reaching the apiserver and stopping it. The entries from v1.4 (ephemeralStorage rename) and v1.6 (migration 46, LINSTOR StorageClass propagation) are not carried over: a cluster on v1.6 is already past them. The page exists in next/ and in the released v1.7/ copy; both get the same text. 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
November 12, 2026 13:47
✅ 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.
 |
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
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.
The Kubernetes app README is dropping its Breaking Changes section. The v1.7 upgrade page is where someone coming from v1.6 reads what changes for tenant clusters, so I moved over the parts that apply to that upgrade and that the page didn't have yet. Both the
next/page and the releasedv1.7/copy get the same text.What's added under "Tenant Kubernetes clusters":
versionandtalosvalues, the health-check settings,maxNodeProvisionTime), and themaxUnhealthy: "50%"default a new pool gets.WorkloadsReadyon aKubernetesresource now covers only the control plane, so waiting on the cluster no longer waits for its workers.KubernetesNodespools before theKubernetesresource.talos.imageFactoryURL,talos.installerRepository,talos.registryMirrorsandosImage, and a pool'sosImage.factory.imageFactoryURLwins over itstalos.imageFactoryURL. TheKubernetesresource ignores those talos keys. The platformregistriesvalue never reached Talos workers, and v1.7.1 removes it along with thepatch-containerdSecret.admissionControllersonly takes the plugin names the KamajiControlPlane CRD lists.extraArgsentries now reach the apiserver as written, so spelling kube feature gates both bare andkube:-prefixed, or giving two kube--emulated-versionentries, stops it from starting. The "Before you upgrade" checklist mentions this too.Not carried over: the
ephemeralStorage→diskSizerename (v1.4), and the migration 46spec.versionbump and LINSTOR StorageClass propagation. Both of those shipped in v1.6.0, so a cluster on v1.6 is already past them.I checked that the site builds with
hugoin both the production and development environments and that the new anchor and in-page link resolve.