Skip to content

Release v0.11.9

Choose a tag to compare

@homer6 homer6 released this 31 Oct 21:31
· 126 commits to main since this release
3a7cac6

Released: 2026-10-31 · Branch: main · Previous: v0.11.8 (2026-10-31).

A patch release: the hub Prometheus writes its configuration, so it federates every cluster and evaluates the hub's alert
rules. After v0.11.7 both hubs and all three agents were Ready, but the hub Prometheus had no scrape targets: prometheus-operator
v0.94 writes no configuration for a Prometheus that sets none of the monitor selectors, so additionalScrapeConfigs and the rule
selector were ignored (Reconciled=True ConfigurationUnmanaged), and every agent reported metricsConnected=false.

v0.11.8 was released but never rolled. This release carries it too: the clusters go from v0.11.7 straight to v0.11.9, with
both fixes.

Measured Value
Resource kinds 54 CRDs in chart/crds (unchanged from v0.11.8)
CRD changes none since v0.11.8; from v0.11.7, ObservabilityHub.spec.users and PixieCloud.spec.users
Operator code the hub Prometheus's selectors
Lake schema nothing vendored
Tests see Verification

What it includes

PR Change
#1102 The hub Prometheus sets a scrapeConfigSelector (and its namespace selector) for the hub's own ScrapeConfigs, of which there are none. It is there so prometheus-operator writes the configuration: the federation jobs and the hub's rules then load. TestHubPrometheusIsPinnedAndScoped fails without it
#1103, from v0.11.8 People can sign in to the Pixie hubs: the organisation's domain, and spec.users (v0.11.8)

What it does not include

  • Any change to the platform charts, Lake or Cloud v1.
  • Live traces through a PxL script are still unproven (observability.md).

Upgrading

  • From v0.11.7, follow v0.11.8's upgrade notes: its two optional CRD fields are widened by the CRD
    rollout (crd-rollout.md), and each hub's file is applied after the roll to add its users.
  • What rolls on each cluster with the operator: the operator, and the zetta-tunnel mesh pods, which carry a container from
    the operator image. No Lake or Cloud v1 workload changes. On the hubs, the hub Prometheus reloads its configuration.

Known issues

Verification

Check Result
go build ./..., go vet ./... pass
go test ./... with envtest (Kubernetes 1.30.3) 3,196 passed, 0 failed, 22 skipped with subtests (1,219 top-level tests). Skipped: the opt-in suites that need a local Postgres, a live zetta-tunnel, a live chart download, and a Prometheus binary
helm lint chart 1 chart(s) linted, 0 chart(s) failed
Not run before the release the hub Prometheus's targets on a live hub; checked after the roll
Pull requests #1102 and #1103 approved by Steve Sperandeo on 2026-10-31
Live rolled after the release; recorded in techops-docs