Skip to content

docs: Hubble enablement snippet doesn't say where to put it (Package values nesting) #2772

Open

Description

@tym83

Problem

The Networking Architecture page, under "Observability with Hubble", gives this snippet to enable Hubble:

cilium:
  hubble:
    enabled: true
    relay:
      enabled: true
    ui:
      enabled: true

It does not say where this goes. That is the non-trivial part:

  1. Editing the cilium HelmRelease directly does not work — the operator reconciles it back, so the change is silently reverted.
  2. The correct place is the cozystack.cilium Package resource, and the values must be nested twice under cilium: — once because the cozystack cilium chart vendors the upstream chart as a subchart aliased cilium, and once for the spec.components.<name>.values wrapper. 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: true

This 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).

Activity

  1. added
    kind/documentationCategorizes issue or PR as related to documentation
    area/networkingIssues or PRs related to networking (ingress, gateway, vpn, metallb, kube-ovn)
    triage/acceptedIndicates an issue is ready to be actively worked on
    priority/backlogGeneral backlog priority. Lower than priority/important-longterm
    on Jun 3, 2026
  2. dvc commented on Jun 8, 2026

    @dvc
    Contributor

    PackageSource cozystack.cilium not found

  3. dvc commented on Jun 8, 2026

    @dvc
    Contributor

    Works for me (partially):

    apiVersion: cozystack.io/v1alpha1
    kind: Package
    metadata:
      name: cozystack.networking
      namespace: cozy-system
    spec:
      variant: kubeovn-cilium
      components:
        cilium:
          values:
            cilium:
              hubble:
                enabled: true
                relay:
                  enabled: true
                ui:
                  enabled: true

    hubble-relay doesn't start:

    msg="Starting gRPC server..." subsys=hubble-relay options="{peerTarget:hubble-peer.cozy-cilium.svc.cluster.local.:443 retryTimeout:30000000000 listenAddress::4245 healthListenAddress::4222 metricsListenAddress: log:0xc0004959b0 serverTLSConfig:<nil> insecureServer:true clientTLSConfig:0xc000495de0 clusterName:default insecureClient:false observerOptions:[0x2743fc0 0x27440a0] grpcMetrics:<nil> grpcUnaryInterceptors:[0x27e0240] grpcStreamInterceptors:[0x27e0300]}"
    ...
    msg="Failed to create peer notify client for peers change notification; will try again after the timeout has expired" subsys=hubble-relay error="rpc error: code = Unavailable desc = name resolver error: produced zero addresses"
    

    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

  4. added
    area/ciliumIssues or PRs related to Cilium (agent, operator, Gateway API, network policy, LB-IPAM)
    on Aug 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/ciliumIssues 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)kind/documentationCategorizes issue or PR as related to documentationpriority/backlogGeneral backlog priority. Lower than priority/important-longtermtriage/acceptedIndicates an issue is ready to be actively worked on

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions