Skip to content

Release v0.11.11

Choose a tag to compare

@homer6 homer6 released this 31 Oct 23:15
· 112 commits to main since this release
4df5988

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

A patch release: the Pixie UI can run scripts. Signed in and with scripts loaded, running px/cluster failed with
"Server error, http status code: 0". Envoy serves gRPC-web on the proxy's port 4444, and its CORS allowed only upstream's
dev.withpixie.dev, so the browser's preflight for ExecuteScript got 403. The release also makes a configuration change roll
the pods that read it
: v0.11.10's script bundle URL reached the API server but not the proxy, which kept serving the old one.

Measured Value
Resource kinds 54 CRDs in chart/crds (unchanged)
CRD changes none
Operator code the PixieCloud rendering (proxy-envoy-config), and a ConfigMap fingerprint on every Pixie pod template (Cloud and Vizier)
Lake schema nothing vendored
Tests see Verification

What it includes

PR Change
#1117 Envoy's CORS origin becomes the hub's domain (suffix, so work.<domain> is covered); rendering fails if the vendored origin ever disappears. orama.cloud/pixie-config on every Pixie pod template is a hash of the rendered ConfigMaps it reads, so a change rolls exactly those pods. TestPixieCloudRendersNoUpstreamDomain (no rendered object names withpixie.dev, withpixie.ai, px.dev or gcr.io/pixie-oss) and TestPixieConfigChangeRollsThePodsThatReadIt

What it does not include

  • Any change to the platform charts, Lake or Cloud v1.
  • The fix for the hub Prometheus not reaching the production leaves
    (#1111).

Upgrading

  • No CRD changes.
  • Every Pixie pod restarts once: the hub on the managing cluster and on nonprod, and the agent on all three leaves, because each
    pod template gains the fingerprint. Pixie keeps its traces in memory, so each node's recent trace data is lost. No Lake or Cloud v1
    workload changes.
  • People reaching the UI forward the proxy's port 4444 too (script runs), as well as 443.

Known issues

  • #1111: ObservabilityClusterUnreachable fires falsely for the
    production leaves.
  • #1104: kuberesolver 401 log noise.
  • 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) 3,198 passed, 0 failed, 22 skipped with subtests (1,221 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 a script run through a live hub; checked after the roll
Pull request #1117 approved by Steve Sperandeo on 2026-10-31
Live rolled after the release; recorded in techops-docs