What changed in gorizond-cluster 0.5.x​

• Switched Fleet deployment to HelmOp for headscale/k3s with automatic namespace creation.
• Hardened name handling for downstream resources to fit DNS-1123 (max 63 chars) and avoid invalid Rancher names.
• Added validation for gorizond cluster names to prevent invalid provisioning clusters.

Compatibility and cleanup notes​

• 0.5.x is backward compatible with clusters provisioned via 0.4.x.
• The headscale/k3s cleanup format changed: instead of a Fleet Bundle we now use HelmOp.
• When deleting older clusters, manually clean up the legacy Fleet Bundle. Ideally, replace old clusters fully to avoid mixed cleanup paths.

GitOps backbone: fleet-gitops​

We use fleet-gitops as a bootstrap repository for Fleet. It is a Helm chart that renders Fleet GitRepo and HelmOp resources from values.yaml, so one repo becomes the single source of truth for everything from the runtime cluster to core services and databases.

How it is structured today:

• fleet-local repos for platform control plane: fleet-gorizond-cluster (gorizond-cluster controller + charts), fleet-workspace-controller, fleet-cert-manager, yookassa-url-generator, docusaurus, jspolicy-for-autoscaler, and fleet-clusters.
• fleet-default repos for shared runtime workloads: fleet-cert-manager and fleet-gorizond-database.
• HelmOps for infra charts like jspolicy and longhorn.

Operational details we rely on:

• Fleet targets clusters by labels like <name>=enabled, plus optional cluster selectors/groups for extra scoping.
• paths allows pointing GitRepos directly at chart or policy subfolders.
• Drift correction is enabled in the generated Fleet resources.

How to upgrade​

• In your GitOps/Fleet bundle set chartVersion of gorizond-cluster-controller to 0.5.x (tag v0.5.x).
• If you manage infrastructure via fleet-gitops, update the controller bundle values there and let Fleet reconcile.
• Roll out via Fleet/Helm and wait for BundleDeployment to reach Ready and controller pods to restart.

How to verify​

• New headscale/k3s namespaces are created automatically by HelmOp for fresh clusters.
• Creating a cluster with an invalid name is rejected before provisioning.
• Controller logs show clean reconcile and Rancher resources use DNS-1123-safe names.

What changed​

• v0.4.0 — Billing finalizer blocks deletion until balance is transferred; controller moves the remaining amount and keeps related Cluster resources consistent. This prevents losing funds when deleting billing.
• v0.4.1 — Reworked FleetBundle reconcile: only targeted objects are updated, unrelated resources are left intact so Fleet UI/extension stays available when cleaning workspaces.
• v0.4.2 — K3S/Headscale chart versions are configurable via environment; upgrade to the latest 0.4.2 patch is recommended.

Full notes: v0.4.0, v0.4.1, v0.4.2; diff v0.3.0…v0.4.2.

How to upgrade​

• In your GitOps/Fleet bundle set chartVersion of gorizond-cluster-controller to 0.4.2 (tag v0.4.2).
• Roll out via Fleet/Helm and wait for BundleDeployment to reach Ready and controller pods to restart.

How to verify​

• When attempting to delete a Billing with balance, the resource stays Terminating until the controller transfers the balance; funds are preserved.
• After deleting a test Fleet workspace, the Fleet extension in Rancher remains available; other workspaces can still be created/deleted.
• Controller logs are clean for Billing/FleetBundle reconcile; probes/metrics stay green.

Add billing CRDs and controller logic for handling billing events and cluster billing status updates. This includes:

1. New CRDs for Billing and BillingEvent resources
2. Controller logic to:
   • Track cluster billing status
   • Generate periodic billing events
   • Process billing events to update balances
3. Configuration options to enable/disable billing controller
4. Dependency updates and cleanup

Current Issues:

• You can delete billing and lose the entire balance, including both positive and negative balances.
• When deleting all fleet workspaces, the user loses the fleet UI, resulting in the inability to create or delete fleet workspaces anymore.

Today the first alpha version of gorizond was released, cluster creation and version update are available, there may be many errors, but this is normal)