Aleksei Sviridkin 0a1bc0d547 docs(capi): correct the reason capmox stays on v0.7 ...

capmox v0.8 still serves v1alpha1 for its machine and cluster CRDs
through a conversion webhook, so the v1alpha1 templates the
kubernetes-nodes chart renders would still be accepted. What holds
capmox back is the move to the v1beta2 contract and v1alpha2 storage,
which has not been tried against those templates and should land
together with in-cluster IPAM v1.1.

Suggested-by: Marian Koreniuk <moriarti@cp.if.ua>
Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-10-13 17:29:09 +03:00

..

apps

fix(kubernetes): keep cluster-autoscaler on the v1beta1 Cluster API

2026-10-12 23:34:18 +03:00

core

fix(e2e): keep chainsaw asserts polling through transient API errors (#4867)

2026-10-12 17:25:39 +03:00

extra

fix(etcd): leave compaction to etcd and pass the real quota to defrag

2026-10-11 20:21:26 +03:00

library

feat(kubernetes-nodes): let CDI trust a self-hosted Talos image factory

2026-10-10 22:36:49 +03:00

system

docs(capi): correct the reason capmox stays on v0.7

2026-10-13 17:29:09 +03:00

tests/cozy-lib-tests

feat(kubernetes-nodes): let CDI trust a self-hosted Talos image factory

2026-10-10 22:36:49 +03:00