cozystack/cmd
Andrei Kvapil af320a86a0
fix(telemetry): use APIReader instead of cached client in operator
The cozystack-operator's manager cache is filtered to only include
specific secrets and namespaces with certain labels. This caused
telemetry collection to fail because resources like kube-system
namespace, nodes, services, and PVs were not in the cache.

Switch to using mgr.GetAPIReader() which bypasses the cache and
queries the API server directly. This is appropriate for telemetry
since it only runs every 15 minutes.

Co-Authored-By: Claude <noreply@anthropic.com>
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
2026-01-27 18:06:30 +01:00
..
backup-controller fix setup cache for backupClasses 2026-01-22 12:59:42 +04:00
backupstrategy-controller fix setup cache for backupClasses 2026-01-22 12:59:42 +04:00
cozypkg feat(cozypkg): add cross-platform build targets with version injection 2026-01-15 17:18:01 +01:00
cozystack-api [cozystack-api] Implement TenantNamespace, TenantModules, TenantSecret and TenantSecretsTable resources 2025-09-24 18:27:54 +02:00
cozystack-controller refactor(telemetry): split telemetry between operator and controller 2026-01-19 13:52:15 +01:00
cozystack-operator fix(telemetry): use APIReader instead of cached client in operator 2026-01-27 18:06:30 +01:00
flux-plunger feat(platform): add flux-plunger controller 2026-01-19 13:20:08 +01:00
kubeovn-plunger [kubeovn] Implement the KubeOVN plunger 2025-09-11 02:11:58 +03:00
lineage-controller-webhook [lineage] Separate webhook from cozy controller 2025-10-14 10:50:28 +03:00