Repository navigation
Release v0.11.5
Released: 2026-10-31 · Branch: main · Previous: v0.11.4 (2026-10-30).
A patch release: Pixie's release is committed, so the observability hubs and agents can install. Until now every
ObservabilityHub and ObservabilityAgent stayed Pending on ObservabilityProvider pixie does not exist, which is why
ObservabilityAgentNotReady and ObservabilityHubUnreachable kept firing for orama-production-cluster-02 and -03.
| Measured | Value |
|---|---|
| Resource kinds | 54 CRDs in chart/crds (unchanged) |
| CRD changes | none |
| Operator code | none (one new test) |
| Lake schema | nothing vendored |
| Tests | see Verification |
What it includes
| PR | Change |
|---|---|
| #1085 | config/clusters/observability-provider.yaml: the ObservabilityProvider pixie, built from oramasearch/pixie at the vendored commit 4b445e0b7907 plus hack/pixie-patches/0001–0004: Vizier 0.14.16-pre-orama.1, Cloud 0.1.10-pre-orama.1, CLI 0.8.9-pre-orama.1, and 27 images, each a private oramasearch/pixie-* repository pinned by digest (the 8 dependency images are mirrors with their upstream's digest). The build patches 0002 (every image named pixie-*), 0003 (143 Go licences recorded, so the build does not depend on pkg.go.dev) and 0004 (the UI bundle's stamp values quoted for Bazel 7), and the build recipe that made the release. TestCommittedPixieReleaseIsInstallable fails when the operator's Pixie commit or image keys move away from the committed release. The sample drops cloud-plugin-load-db, a key the operator refuses |
(#455 tracked the build.)
What it does not include
- Any change to the operator's code, the hubs, the agents or the platform charts.
- Pixie has not run on a cluster before this release (observability.md).
Upgrading
- No CRD changes. The CRD rollout (crd-rollout.md) runs as for any release and changes nothing.
- The provider is applied to the managing cluster from
config/clusters/observability-provider.yaml. Once it exists,
every hub and every agent installs at once: there is no setting that holds production back while nonprod goes first. - 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.
Known issues
- Unchanged from v0.11.1.
- The managing cluster has a single node; the production hub requests about 1.8 CPU and 7 GiB of the about 2.3 CPU and 18 GiB
free when the provider was applied.
Verification
| Check | Result |
|---|---|
go build ./..., go vet ./... |
pass |
go test ./... with envtest (Kubernetes 1.30.3) |
3,193 passed, 0 failed, 22 skipped with subtests (1,216 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 linted, 0 failed |
| Pull request | reviewed by Steve Sperandeo on 2026-10-31; not re-tested in review, so this run is the first of the merged tree |
| Live | rolled to every cluster after the release, and the provider applied; recorded in techops-docs |