Released: 2026-10-31 · Branch: main · Previous: v0.11.11 (2026-10-31).
A patch release: one Pixie hub shows every cluster, and Pixie keeps each user's settings. Production's hub on the managing
cluster now takes the managing cluster itself and nonprod, as well as orama-production-cluster-02 and -03 (Steve, 2026-10-31,
replacing #456's one hub per purpose). The welcome tour no longer comes back on every page load: the bootstrap now writes the
per-user rows Pixie's settings are saved in.
| Measured |
Value |
| Resource kinds |
54 CRDs in chart/crds (unchanged) |
| CRD changes |
ObservabilityAgent: spec.clusterRef optional (empty is the managing cluster), new optional spec.alerting |
| Operator code |
the Pixie bootstrap (per-user rows), the observability purpose rule, agent alert routing |
| Lake schema |
nothing vendored |
| Tests |
see Verification |
What it includes
| PR |
Change |
| #1124 |
Settings (#1121). The bootstrap gives each Pixie user its user_attributes and user_settings rows, which Pixie's own user creation writes and its settings updates need; existing users get them on the next reconcile. The bootstrap role gains SELECT, INSERT on the two tables. The managing cluster's agent (#1122). An ObservabilityAgent with no clusterRef runs on the managing cluster, beside production's hub without a link, registered under the hub's name. Nonprod on production's hub (#1122). The managing cluster's hub accepts nonprod agents; production still never reports to a nonprod hub. An agent may name its own alert receivers (spec.alerting); a nonprod agent on production's hub pages only through those, so production's receiver Secrets never reach nonprod. config/clusters: the managing cluster's agent in observability-hub.yaml; nonprod's agent reports to production's hub and keeps #monitoring-stg; nonprod's own hub is retired from the file |
What it does not include
- Any change to the platform charts, Lake or Cloud v1.
- Applying the new agent files or deleting nonprod's hub: each needs Steve's consent after the roll.
- The fix for the hub Prometheus not reaching the production leaves
(#1111).
Upgrading
- Apply the CRDs first:
ObservabilityAgent drops clusterRef from required and gains alerting. Additive; existing agents
are unchanged.
- No pod restarts from the operator code itself; the hub's bootstrap writes two rows per user on its next pass.
- After the roll, with consent: apply
config/clusters/observability-hub.yaml (the managing cluster's agent: Pixie's node agents
on the managing cluster) and config/clusters/orama-nonprod-cluster-01/observability.yaml (nonprod's agent moves to production's
hub: its Vizier re-registers there and its in-memory trace history restarts), then delete ObservabilityHub/nonprod on the
managing cluster, which removes nonprod's Pixie Cloud and its databases (sign-ins only).
- What one hub costs: nonprod gets a PeerLink to production's hub like each production cluster: vzconn only, its own deploy
key, the hub's CA; the hub reads back its read-only metrics proxy. Nonprod's "cluster lost" alerts come from the hub's rules and go
to #monitoring.
Known issues
- #1111:
ObservabilityClusterUnreachable fires falsely for the
production leaves.
- #1104: kuberesolver 401 log noise on the hub's API server.
- Pixie shows clusters as degraded ("non-operator version of Pixie"): cosmetic, because this operator installs Vizier instead of
Pixie's own operator.
- Licensing: Pixie's eBPF programs are GPL-2.0 (orama-bridge#268).
Verification
| Check |
Result |
go build ./..., go vet ./... |
pass |
go test ./... with envtest (Kubernetes 1.30.3) |
not run for this release, on Steve Sperandeo's instruction ("we can skip the test this time"); stopped while running. On #1124's branch, go test ./... -count=1 passed (7 packages, no failures; run without envtest assets, so envtest suites may have skipped) |
go test ./cmd/ |
passes on the release branch, TestReleaseVersionIsDocumented included |
helm lint chart |
1 chart(s) linted, 0 chart(s) failed |
| Pull request |
#1124 approved by Steve Sperandeo on 2026-10-31 |
| Live |
rolled after the release; recorded in techops-docs |