Repository navigation
docs: Hubble enablement snippet doesn't say where to put it (Package values nesting) #2772
Copy link
Copy link
Open
Labels
area/ciliumIssues or PRs related to Cilium (agent, operator, Gateway API, network policy, LB-IPAM)Issues or PRs related to Cilium (agent, operator, Gateway API, network policy, LB-IPAM)area/networkingIssues or PRs related to networking (ingress, gateway, vpn, metallb, kube-ovn)Issues or PRs related to networking (ingress, gateway, vpn, metallb, kube-ovn)kind/documentationCategorizes issue or PR as related to documentationCategorizes issue or PR as related to documentationpriority/backlogGeneral backlog priority. Lower than priority/important-longtermGeneral backlog priority. Lower than priority/important-longtermtriage/acceptedIndicates an issue is ready to be actively worked onIndicates an issue is ready to be actively worked on
Description
Problem
The Networking Architecture page, under "Observability with Hubble", gives this snippet to enable Hubble:
cilium:
hubble:
enabled: true
relay:
enabled: true
ui:
enabled: trueIt does not say where this goes. That is the non-trivial part:
- Editing the
ciliumHelmRelease directly does not work — the operator reconciles it back, so the change is silently reverted. - The correct place is the
cozystack.ciliumPackageresource, and the values must be nested twice undercilium:— once because the cozystack cilium chart vendors the upstream chart as a subchart aliasedcilium, and once for thespec.components.<name>.valueswrapper. The snippet only shows the innermost layer, so it's easy to land it at the wrong depth where it has no effect.
Expected
The snippet should be shown in full, in context:
apiVersion: cozystack.io/v1alpha1
kind: Package
metadata:
name: cozystack.cilium
namespace: cozy-system
spec:
variant: default
components:
cilium:
values:
cilium:
hubble:
enabled: true
relay:
enabled: true
ui:
enabled: trueThis matches the pattern already documented for MetalLB in Overwriting Component Parameters (components.metallb.values.metallb.frrk8s). A one-line cross-link from the Hubble section to that page would also help.
Related: #749 (Hubble as a Grafana observability source — separate request).
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area/ciliumIssues or PRs related to Cilium (agent, operator, Gateway API, network policy, LB-IPAM)Issues or PRs related to Cilium (agent, operator, Gateway API, network policy, LB-IPAM)area/networkingIssues or PRs related to networking (ingress, gateway, vpn, metallb, kube-ovn)Issues or PRs related to networking (ingress, gateway, vpn, metallb, kube-ovn)kind/documentationCategorizes issue or PR as related to documentationCategorizes issue or PR as related to documentationpriority/backlogGeneral backlog priority. Lower than priority/important-longtermGeneral backlog priority. Lower than priority/important-longtermtriage/acceptedIndicates an issue is ready to be actively worked onIndicates an issue is ready to be actively worked on
Activity
dvc commentedon Jun 8, 2026
PackageSource cozystack.cilium not founddvc commentedon Jun 8, 2026
Works for me (partially):
hubble-relay doesn't start:
hubble-ui has no ingress. Start via port-forwarding doesn't show any info in all namespaces, i've tested.
cozy version 1.1.3