3 Commits

Include renames

Author	SHA1	Message	Date
Myasnikov DaniilandClaude Opus 4.8	2e7f14acb7	test(version): clear ambient COZYSTACK_VERSION in the unset case ... Address review feedback from coderabbitai on pkg/version/version_test.go: the env-unset case only skipped t.Setenv, so a COZYSTACK_VERSION inherited from the test runner would make it skip the baked-fallback path it is meant to cover. Unset the variable (restoring it on cleanup) for that case. Assisted-By: Claude <noreply@anthropic.com> Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>	2026-07-06 10:03:56 +05:00
Myasnikov DaniilandClaude Opus 4.8	fd7fcbda4e	refactor(operator): read platform version from env (decouple from build) ... The operator's platform version was baked into the image at build time (`-ldflags -X pkg/version.Version` from `git describe`), so a `vX.Y.Z-rc.N` image literally carried the rc string. That blocks promoting a release-candidate to stable by retag: the bits would still self-report the rc version. Resolve the version from the COZYSTACK_VERSION env var at runtime, falling back to the build-time value when unset (local builds still work). The installer chart threads `cozystackOperator.platformVersion` into the operator Deployment as that env var, and `make manifests` stamps it into the kubectl-apply release artifacts. The same image bits can now report any release name, so promotion needs no rebuild. The only behavioral reader is the telemetry metric `cozy_cluster_info{cozystack_version=...}`; cozypkg/check-readiness keep their own build-time Version and are unaffected. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>	2026-07-06 10:03:46 +05:00
Andrei KvapilandClaude	987a74ae5a	refactor(telemetry): split telemetry between operator and controller ... Split telemetry collection between cozystack-operator and cozystack-controller: cozystack-operator now collects cluster-level metrics: - cozy_cluster_info (cozystack_version, kubernetes_version) - cozy_nodes_count (os, kernel) - cozy_cluster_capacity (cpu, memory, nvidia.com/* resources) - cozy_loadbalancers_count - cozy_pvs_count (driver, size) - cozy_package_info (name, variant) cozystack-controller now collects application-level metrics: - cozy_application_count (kind) - counts HelmReleases per ApplicationDefinition Other changes: - Add pkg/version for build-time version injection via ldflags - Remove --cozystack-version flag (version now embedded at build time) - Remove bundle/oidc configuration from telemetry (replaced by package_info) - Remove cozy_workloads_count metric (replaced by cozy_application_count) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: Andrei Kvapil <kvapss@gmail.com>	2026-01-19 13:52:15 +01:00