Skip to content

Implement team-specific multitenant runtime wiring and standardize Kubernetes tests on kind#331

Open
bill-ph wants to merge 9 commits intomainfrom
team-specific-runtime
Open

Implement team-specific multitenant runtime wiring and standardize Kubernetes tests on kind#331
bill-ph wants to merge 9 commits intomainfrom
team-specific-runtime

Conversation

@bill-ph
Copy link
Collaborator

@bill-ph bill-ph commented Mar 19, 2026

Summary

  • add team-specific runtime resolution for worker namespace, service account, and runtime config secret selection
  • update team router reconciliation to rebuild stacks on runtime or memory budget changes and keep the existing stack on replacement failure
  • extend K8s worker pool wiring so workers can consume team-specific runtime config secrets
  • render managed warehouse runtime artifacts from the config-store contract, including safer DuckLake metadata-store and S3 handling
  • standardize local and CI Kubernetes testing on kind, keep OrbStack as an optional path, and reorganize K8s manifests into shared/, kind/, and orbstack/
  • update docs and the multitenant plan to reflect the new runtime-config ownership and completed worker-pod work

Testing

  • just lint
  • go test -tags kubernetes ./controlplane -count=1
  • go test ./tests/k8s -count=1
  • go test -c -tags k8s_integration ./tests/k8s
  • just test-k8s-integration

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant