IvanHunters a00421aa17 feat(kubernetes-api): warn on Phase 2 removed fields and document them ...

The Kubernetes CR still accepts and stores spec.nodeGroups, spec.nodeHealthCheck
and spec.maxNodeProvisionTime after the Phase 2 split (the adoption migration
leaves them on an upgraded CR rather than rewriting parent values mid-upgrade),
but they no longer render anything, so an operator scaling via
spec.nodeGroups.<x>.minReplicas silently got nothing.

Emit a non-blocking client-facing admission warning on Create/Update when any
of these fields is present, pointing the operator at the KubernetesNodes
resources. A hard rejection is intentionally avoided: it would break edits to
already-upgraded clusters that still carry the fields. Also enumerate all the
Phase 2 breaking changes (three removed fields, two KubernetesNodes
immutability rules, the 32-char cluster-name cap) in the chart README.

Signed-off-by: IvanHunters <xorokhotnikov@gmail.com>

2026-08-21 00:40:44 +03:00

..

apis

fix(api): declare OpenAPIModelName for core and sdn types

2026-08-14 13:12:28 +05:00

apiserver

feat(sdn): wire SecurityGroup into the aggregated apiserver

2026-06-22 16:35:10 +03:00

cmd/server

feat(api): typed waitStrategy/healthCheckExprs for kstatus readiness

2026-07-16 16:45:16 +05:00

config

docs(api): note disableWait silently defeats healthCheckExprs

2026-07-16 16:48:33 +05:00

generated

test(api): guard published openapi definition names and refs

2026-08-14 13:12:39 +05:00

lineage

feat: Gateway API support via Cilium

2026-05-25 17:07:02 +03:00

ovnstatus

[kubeovn] Implement the KubeOVN plunger

2025-09-11 02:11:58 +03:00

registry

feat(kubernetes-api): warn on Phase 2 removed fields and document them

2026-08-21 00:40:44 +03:00

version

test(version): clear ambient COZYSTACK_VERSION in the unset case

2026-07-06 10:03:56 +05:00