Skip to content

Release v0.11.7

Choose a tag to compare

@homer6 homer6 released this 31 Oct 18:48
· 139 commits to main since this release
2066016

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

A patch release: Pixie's metadata index is created as soon as OpenSearch is ready, so the indexer starts and the
observability hubs can become Ready. After v0.11.6 both hubs were stuck at 19/20: the indexer exits when its index
md_entities_9 is missing, the hub is not Ready without the indexer, and the operator created the index only once the hub was
Ready.

Measured Value
Resource kinds 54 CRDs in chart/crds (unchanged)
CRD changes none
Operator code the PixieCloud bootstrap's order
Lake schema nothing vendored
Tests see Verification

What it includes

PR Change
#1098 The bootstrap takes OpenSearch's readiness apart from the hub's: it creates the metadata index once pixie-search is Ready, and does the rest (the administrator, the organisation, the deploy keys) once the hub is Ready, as before. TestPixieCloudBootstrapIssuesAndRevokesPerClusterKeys now expects the index and no keys with only OpenSearch ready
#1072 Docs: how people reach Perses, Prometheus, Alertmanager and the Pixie UI (kubectl port-forward, nothing public), and Verify records that the platform charts run on all four clusters

What it does not include

  • Any change to the platform charts, Lake or Cloud v1.
  • The Viziers connecting to their hub and live traces are still unproven
    (observability.md).

Upgrading

  • No CRD changes. The CRD rollout (crd-rollout.md) runs as for any release and changes nothing.
  • 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 operator then creates the index and the indexer
    starts.

Known issues

  • Unchanged from v0.11.6.
  • #1096: a CloudflareR2Bucket already gone keeps its finalizer;
    v1-dev-uploads gets 403 on permission groups.

Verification

Check Result
Full suite (go test ./... with envtest) not run for this release, on Steve Sperandeo's instruction ("skip testing again for this one... let's get it deployed asap")
The PR's own tests go test ./cmd/ ./internal/controller/ passed on #1098's branch (per the PR); the changed test fails without the fix
go test ./cmd/ -run TestReleaseVersionIsDocumented pass, on the release branch
helm lint chart 1 chart(s) linted, 0 chart(s) failed
Pull requests #1098 and #1072 approved by Steve Sperandeo on 2026-10-31
Live rolled to every cluster after the release; recorded in techops-docs