You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 46f2104
Browse filesBrowse the repository at this point in the historyBrowse files
cozyplane: split the API group; PVC-backed apiserver etcd
Sync of the cozyplane charts after the API-group split (lllamnyp/cozyplane,
docs/api-groups.md).
The tenant kinds (VPC, Port, SecurityGroup, HostFirewall, ...) are now served
ONLY by the aggregated apiserver and have no CRDs at all. One group served by
two mechanisms cannot work: a CRD keeps publishing its OpenAPI paths after an
APIService takes the group over, the two specs collide on duplicated paths, the
group's schema never serves, and `kubectl apply` of every cozyplane object
fails client-side with "failed to download openapi" while core types keep
working. That is why the takeover is gone rather than fixed — there is nothing
to take over.
The CNI package now ships only the LOCAL group's CRDs
(local.sdn.cozystack.io): FabricIP, the underlay IPAM claim, whose dependency
floor is the kube API and nothing else — everything above it, cert-manager and
etcd and the aggregated server included, runs as default-network pods.
The apiserver's etcd moves from tmpfs to a PVC on the replicated class. Its
objects are cluster state: memory-backed, a full-cluster restart loses every
VPC, Port and policy — and a node reboot is exactly that. This is the follow-up
the values file already promised ("a persistent mode is a follow-up once storage
is sequenced"), so the component now dependsOn cozystack.linstor. No cycle:
linstor depends on the CNI, not on this.
Also new in the charts: NetworkPolicy/HostFirewall/SecurityGroup RBAC for the
agent, FabricIP RBAC for the agent and controller.
Assisted-by: LLM
Signed-off-by: Timofei Larkin <[email protected]>
0 commit comments