Summary
license.type: home is offered as a documented value in values.yaml, but the chart's architecture makes it impossible to actually run under a Home license: every component (ingester, querier, compactor, processor) registers as a separate node, and the Home license's license server enforces a hard single-node limit at runtime.
Environment
- OS / Kubernetes distribution: Talos Linux
- Kubernetes version: server
v1.32.2 (client v1.34.1)
- Helm chart:
influxdb3-enterprise version 0.7.3, appVersion 3.9.3
- Deployment: standard
helm install, ingester.replicas: 1, querier.replicas: 1, default compactor
- License:
license.type: "home", verified via email
Steps to reproduce
- Install the chart with
license.type: "home" and a verified license email
- Leave
ingester, querier, and compactor at their default enabled state (1 replica each)
- Observe pod logs
Expected behavior
Either:
- The deployment starts successfully under a Home license, or
- The chart documents/validates up front that
license.type: home is incompatible with its default topology, rather than letting it fail at container startup
Actual behavior
Ingester and compactor pods crash on startup:
INFO influxdb3_enterprise_licensing::trial: Home Enterprise license verified
INFO influxdb3_lib::commands::serve: valid license found, happy data crunching
Serve command failed: only one node is allowed when using Home License
The license itself validates correctly — the failure is purely about node count.
Root cause
Each component's --mode is a hardcoded literal in its own template, not exposed via values.yaml:
templates/ingester-statefulset.yaml: - --mode=ingest
templates/querier-statefulset.yaml: - --mode=query
templates/compactor-statefulset.yaml: - --mode=compact
templates/processor-statefulset.yaml: - --mode=process
There's no template or values field that produces a combined --mode=all node, which is what a single-node Home license deployment would require. So regardless of how replicas or enabled are set per component, a Home-license-compatible deployment isn't reachable through this chart's current templates — disabling querier/compactor doesn't help either, since ingester alone can't serve queries.
Related issues
Additional context
In the #core-setup-support Discord channel (Dec 11, 2025), an InfluxData team member stated the newly-released chart "works with the Enterprise Home license as well." That was right around the chart's first 0.1.x releases — if the chart's architecture has changed since then (e.g. an all-in-one mode existed early on and was later replaced by the current specialized-node split), that would explain the discrepancy. If so, it'd be great to get an all-in-one option back; if the statement was inaccurate even then, it'd be good to correct it and document that home/trial license types aren't currently usable with this chart.
Question for maintainers
What's the intended path for Home/Trial license users on this chart — is a combined --mode=all template planned, should ingester support an override to run standalone, or should home/trial be documented as unsupported here (with users pointed to the plain Docker/binary install instead)? Happy to help test or PR once there's a direction.
Summary
license.type: homeis offered as a documented value invalues.yaml, but the chart's architecture makes it impossible to actually run under a Home license: every component (ingester,querier,compactor,processor) registers as a separate node, and the Home license's license server enforces a hard single-node limit at runtime.Environment
v1.32.2(clientv1.34.1)influxdb3-enterpriseversion0.7.3, appVersion3.9.3helm install,ingester.replicas: 1,querier.replicas: 1, default compactorlicense.type: "home", verified via emailSteps to reproduce
license.type: "home"and a verified license emailingester,querier, andcompactorat their default enabled state (1 replica each)Expected behavior
Either:
license.type: homeis incompatible with its default topology, rather than letting it fail at container startupActual behavior
Ingester and compactor pods crash on startup:
The license itself validates correctly — the failure is purely about node count.
Root cause
Each component's
--modeis a hardcoded literal in its own template, not exposed viavalues.yaml:There's no template or values field that produces a combined
--mode=allnode, which is what a single-node Home license deployment would require. So regardless of howreplicasorenabledare set per component, a Home-license-compatible deployment isn't reachable through this chart's current templates — disablingquerier/compactordoesn't help either, sinceingesteralone can't serve queries.Related issues
INFLUXDB3_ENTERPRISE_LICENSE_EMAILenv var not being emitted when usinglicense.existingSecret). That fix doesn't touch node topology, and neither the PR diff nor its review discussion mentions node count or--mode— so it doesn't establish that a multi-node Home license deployment actually works end to end.Additional context
In the
#core-setup-supportDiscord channel (Dec 11, 2025), an InfluxData team member stated the newly-released chart "works with the Enterprise Home license as well." That was right around the chart's first0.1.xreleases — if the chart's architecture has changed since then (e.g. an all-in-one mode existed early on and was later replaced by the current specialized-node split), that would explain the discrepancy. If so, it'd be great to get an all-in-one option back; if the statement was inaccurate even then, it'd be good to correct it and document thathome/triallicense types aren't currently usable with this chart.Question for maintainers
What's the intended path for Home/Trial license users on this chart — is a combined
--mode=alltemplate planned, shouldingestersupport an override to run standalone, or shouldhome/trialbe documented as unsupported here (with users pointed to the plain Docker/binary install instead)? Happy to help test or PR once there's a direction.