Skip to content

Commit 154c4ff

Browse files
myasnikovdaniilmyasnikovdaniil
committed
docs(kubernetes): document moving existing worker pools onto golden images
The platform now writes the image source and the installer prefix into the spec of a new worker pool, and does nothing for a pool that already exists. An operator who wants an existing pool on a golden image has no document that says how, and the obvious attempts go wrong in ways that are easy to miss. Defaults are applied when a pool is read and written back by its first edit, so the pool already carries the public installer prefix explicitly and keeps it unless the same patch replaces it. And a pool that opted out of the golden, or pinned a factory version, carries osImage.factory: a merge patch that only adds osImage.builtin leaves both set, and the pool stops rendering with "set only one of". The same patch has to null the factory, and so does the way back. Put the procedure in the header of the worker image catalog, where an operator looks for everything about goldens, with the checks that make the pool render and the cost of the roll. Say in the pool's field docs that these values are filled in at creation and that an older pool keeps what it has. Assisted-by: LLM Signed-off-by: Myasnikov Daniil <[email protected]>
1 parent 434ed51 commit 154c4ff

6 files changed

Lines changed: 67 additions & 18 deletions

File tree

‎api/apps/v1alpha1/kubernetesnodes/types.go‎

Lines changed: 3 additions & 3 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)