Ivan Okhotnikov
0f60f0703a
Kamaji's controller takes SSA field-ownership on `KamajiControlPlane.spec.deployment.extraVolumes` when it syncs the resource back from the TenantControlPlane, and Helm's subsequent apply (with the same field-manager but a manifest that omits the OIDC volume) then no longer removes it — the tenant apiserver Pod keeps an unmounted-but-declared `authentication-config` volume pointing at a Secret the chart already reaped. Harmless at runtime (the volume is not mounted after the extraVolumeMounts fix), but the CRD gets dirty and the operator wants zero leftovers. Fix: the OIDC bootstrap Job is now rendered for ALL modes (not only `System`/`CustomConfig`). When `mode=None` the Job takes the normalize path — a single `kubectl patch --type=merge` that replaces `spec.deployment.extraVolumes` with the chart baseline (talos-ca + talos-tls-cert). We verified end-to-end that `kubectl patch --type=merge` on this array REPLACES it deterministically (the earlier Helm patch didn't). For `mode=System`/`CustomConfig` the Job continues to apply per-user ClusterRoleBindings inside the tenant cluster, prune stale ones labelled by this release, and patch the pre-rendered `<release>-oidc-kubeconfig` Secret with a real kubeconfig. The Role gains `patch` on the specific `kamajicontrolplanes/<release>` so the normalize path has just enough privilege; nothing else new. The pre-delete cleanup Job stays conditional on `mode != None` — no CRBs to clean up when OIDC was never enabled. Signed-off-by: Ivan Okhotnikov <ivan.okhotnikov@aenix.io>
Cozystack
Cozystack is a free platform and framework for building clouds.
Cozystack is a CNCF Sandbox Level Project that was originally built and sponsored by Ænix.
With Cozystack, you can transform a bunch of servers into an intelligent system with a simple REST API for spawning Kubernetes clusters, Database-as-a-Service, virtual machines, load balancers, HTTP caching services, and other services with ease.
Use Cozystack to build your own cloud or provide a cost-effective development environment.
Use-Cases
-
Using Cozystack to build a public cloud
You can use Cozystack as a backend for a public cloud -
Using Cozystack to build a private cloud
You can use Cozystack as a platform to build a private cloud powered by Infrastructure-as-Code approach -
Using Cozystack as a Kubernetes distribution
You can use Cozystack as a Kubernetes distribution for Bare Metal
Documentation
The documentation is located on the cozystack.io website.
Read the Getting Started section for a quick start.
If you encounter any difficulties, start with the troubleshooting guide and work your way through the process that we've outlined.
Versioning
Versioning adheres to the Semantic Versioning principles.
A full list of the available releases is available in the GitHub repository's Release section.
Contributions
Contributions are highly appreciated and very welcomed!
In case of bugs, please check if the issue has already been opened by checking the GitHub Issues section. If it isn't, you can open a new one. A detailed report will help us replicate it, assess it, and work on a fix.
You can express your intention to on the fix on your own. Commits are used to generate the changelog, and their author will be referenced in it.
If you have a concrete feature request, open an issue. For a cross-cutting or architectural change, open a design proposal in the community repo. For questions or early ideas, use GitHub Discussions. See CONTRIBUTING.md for the full routing.
Community
You are welcome to join our Telegram group and come to our weekly community meetings. Add them to your Google Calendar or iCal for convenience.
License
Cozystack is licensed under Apache 2.0.
The code is provided as-is with no warranties.
Commercial Support
A list of companies providing commercial support for this project can be found on official site.