Skip to content

Release v0.11.8

Choose a tag to compare

@homer6 homer6 released this 31 Oct 21:19
· 132 commits to main since this release
2656a48

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

A patch release: people can sign in to the Pixie hubs. After v0.11.7 both hubs ran, but Pixie turned their
administrator away with "Our system found an issue with your account". Pixie's sign-in refuses a member of an
organisation that has no domain, unless the organisation is named after that member's email
(src/cloud/auth/controllers/login.go, loginSimple). The operator had created the organisation orama without a
domain.

Measured Value
Resource kinds 54 CRDs in chart/crds (unchanged)
CRD changes ObservabilityHub.spec.users and PixieCloud.spec.users, optional lists of emails
Operator code the PixieCloud bootstrap: the organisation's domain, and one sign-in per user
Lake schema nothing vendored
Tests see Verification

What it includes

PR Change
#1103 The organisation gets the administrator's email domain, and a hub bootstrapped without one has it set: the bootstrap role may update orgs.domain_name, and nothing else of an existing row. spec.users: each email gets a generated password in plc/pixie-user-<email>, an identity in Kratos and a user in the organisation; an email removed loses its identity, then its Secret. Both hubs' files list steve@orama.com. Docs: the bootstrap, the Secrets, the CRD reference, and why the UI must be reached on port 443

What it does not include

  • Any change to the platform charts, Lake or Cloud v1.
  • Live traces through a PxL script are still unproven (observability.md).

Upgrading

  • CRDs: two optional fields are added. The CRD rollout (crd-rollout.md) widens them before
    the operator upgrade, as for any release.
  • 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 each hub, on the next pass after the roll: the organisation gets its domain, and sign-in works for the administrator.
  • Then apply each hub's file (config/clusters/observability-hub.yaml, config/clusters/orama-nonprod-cluster-01/observability.yaml)
    to add its users. The operator writes each user's Secret and sign-in within five minutes.

Known issues

  • Unchanged from v0.11.7.
  • #1104: the hub's auth-server, profile-server and api-server
    log a kuberesolver 401 from the Kubernetes API every second. It does not stop sign-in or registration.
  • The proxy redirects <domain> to https://work.<domain>/ without the port, so the UI must be reached on port 443 (techops-docs'
    observability runbook gives two ways).

Verification

Check Result
go build ./..., go vet ./... pass
go test ./... with envtest (Kubernetes 1.30.3) 3,195 passed, 1 failed, 22 skipped with subtests (1,218 top-level tests). The one failure was TestReleaseVersionIsDocumented: the suite started before this page existed. go test ./cmd/ rerun after it was written: pass. Skipped: the opt-in suites that need a local Postgres, a live zetta-tunnel, a live chart download, and a Prometheus binary
The PR's own tests TestPixieCloudBootstrapLetsTheAdministratorAndEveryUserSignIn (new), TestPixieCloudBootstrapIssuesAndRevokesPerClusterKeys and TestPixieBootstrapMatchesVendoredSchema (now covers orgs.domain_name)
helm lint chart 1 chart(s) linted, 0 chart(s) failed
Not run before the release the domain update and the Kratos delete against a live hub; checked after the roll by signing in
Pull request #1103 approved by Steve Sperandeo on 2026-10-31
Live rolled after the release; recorded in techops-docs