Skip to content

Release v0.11.6

Choose a tag to compare

@homer6 homer6 released this 31 Oct 17:46
· 149 commits to main since this release
f73026b

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

A patch release: the faults that stopped both observability hubs after Pixie's release was applied. With v0.11.5 and the
provider applied, each hub's Prometheus crash-looped and Pixie Cloud never started. Three operator faults are fixed here; the
fourth, the Postgres image's missing tag, was fixed in the committed provider on dev (1e912c0f) and applied the same day.

Measured Value
Resource kinds 54 CRDs in chart/crds (unchanged)
CRD changes none
Operator code the hub Prometheus, the Pixie release check, the Pixie prune, Pixie Cloud's dependency ConfigMaps
Lake schema nothing vendored
Tests see Verification

What it includes

PR Change
#1091 The hub Prometheus owns its volume. It set no pod securityContext, so its Azure disk stayed root's and Prometheus (non-root) failed with permission denied on /prometheus. It now runs as uid 1000 with fsGroup 2000, like the platform's kube-prometheus-stack. A Pixie Postgres image must carry its tag: CloudNativePG reads the PostgreSQL version from the tag and refuses an image given by digest alone, so the provider is not Ready until postgres is repo:<version>@sha256:…. config/clusters/observability-provider.yaml already names pixie-postgres:16.15@sha256:34cd4159… (1e912c0f)
#1092 The Pixie prune spares objects another controller owns. CloudNativePG copies the pixie-db Cluster's inherited labels, orama.cloud/pixie: cloud included, onto the ServiceAccount, Services and budget it creates; the prune listed them by that label and deleted them on every pass, so the database pod's token stopped working (Unauthorized). It also tried to delete CNPG's Role and RoleBinding (refused). It now skips an object whose controller is not an orama.cloud kind. pl-sentry-dsn-config is rendered, its three keys empty (Sentry off), as upstream ships it in cloud_deps; without it config-manager stopped at CreateContainerConfigError. Two tests: every ConfigMap key a rendered Cloud pod needs is rendered, and the prune leaves a CNPG-owned object alone

What it does not include

  • Any change to the platform charts, Lake or Cloud v1.
  • Pixie Cloud has not yet started on a cluster: past the database, Kratos and Hydra, the bootstrap, the deploy keys and the
    Viziers 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. On the two hubs (the managing cluster and nonprod), the hub Prometheus is re-created with its new
    securityContext. No Lake or Cloud v1 workload changes.
  • A pixie-db-1 pod started before the upgrade may still hold a token for a ServiceAccount the old prune deleted. If it keeps
    failing with Unauthorized once CNPG has recreated the account, the pod must be replaced.

Known issues

  • Unchanged from v0.11.5.
  • Nonprod's lake controller errors on workspace namespaces that no longer exist
    (#1090).

Verification

Check Result
Full suite (go test ./... with envtest) not run for this release, on Steve Sperandeo's instruction ("please skip the tests for this one and cut and deploy")
The PRs' own tests go test ./cmd/ ./internal/controller/ passed on each PR's own branch (#1091 per its description, #1092 locally); each new test fails without its fix. The merged tree of both was not tested
go test ./cmd/ -run TestReleaseVersionIsDocumented pass, on the release branch
helm lint chart 1 chart linted, 0 failed
Pull requests #1091 and #1092 approved by Steve Sperandeo on 2026-10-31 ("release and deploy these")
Live rolled to every cluster after the release; recorded in techops-docs