Repository navigation
feat(tenant): model the Tenant tracingCentral field #64
Description
cozystack/cozystack#3775 adds a field to the Tenant application, so cozystack_tenant needs it modelled.
The field. tracingCentral (boolean, default false) in packages/apps/tenant/values.schema.json: it sends the tenant's traces to the shared VictoriaTraces store in tenant-root instead of a per-tenant backend. It takes effect only together with monitoring: true on the same tenant, and only once tenant-root hosts the store; without that, the tenant's monitoring render fails with a message naming the prerequisite.
What the provider needs, following the existing monitoring attribute:
- a
tracing_centralattribute (Boolean, Optional) on thecozystack_tenantresource and data source, ininternal/provider/tenant_model.go,tenant_resource.goandtenant_data_source.go, with its expand/flatten and tests; - the
api/apps/v1alpha1pin bumped once #3775 is merged, so the top-level field guard sees it.
Not needed. cozystack/cozystack#4648 adds tracingCentralTenantBytesPerSecond to the Monitoring module, and #3775 adds tracingCentralHost there; cozystack_tenant_module is a marker without values, so neither needs a change here.
Activity
feat(monitoring,tenant): shared-central tracing topology (phase 4) (#…
scooby87 commentedon Oct 6, 2026
Status update: the upstream side is merged, but this cannot land yet.
Upstream. cozystack/cozystack#3775 added
tracingCentralto the Tenant (TracingCentral boolwith+kubebuilder:default:=false, schema{"type": "boolean", "default": false}), and cozystack/cozystack#4648 changed only its description. The field works only together withmonitoring: trueon the same tenant and with tenant-root hosting the shared store; otherwise the chart fails the tenant's monitoring render with a message naming the prerequisite, so the provider has nothing to validate here.Blocker. The provider pins
github.com/cozystack/cozystack/api/apps/v1alpha1to a released tag, and no tag contains the field yet: the latest isapi/apps/v1alpha1/v1.6.4. Pinning to amainpseudo-version instead is not a small change either:httpcachewas renamed tovalkeyin the module, so the provider's tests no longer build, and the bump also bringsgatewayClassandcomputeplaneon the Tenant plus new fields on other kinds, which the spec-coverage guards then require. So this waits for the firstapi/apps/v1alpha1v1.7 tag and will most likely go in together with the rest of the v1.7 sync.Correction to "Not needed". As merged, cozystack/cozystack#4648 did not add
tracingCentralTenantBytesPerSecondto the Monitoring module: it is a platform key,monitoring.tracingCentralTenantBytesPerSecondinpackages/core/platform/values.yaml, carried to tenants through_cluster. The conclusion still holds, because the platform package is outside the provider's typed surface andcozystack_tenant_moduleis a marker without values.Planned change once the tag exists. A
tracing_centralattribute modelled exactly likemonitoring: Optional + Computed withbooldefault.StaticBool(false)to match the schema default, expand/flatten, the data source attribute, and tests.scooby87 commentedon Oct 8, 2026
Implemented in #67. The pin goes to the cozystack main commit that merged cozystack/cozystack#4648, so the PR also carries the adaptations that commit forces on the provider; the PR description explains why.
scooby87 commentedon Oct 14, 2026
Done in #67.