feat(stack): pluggable backend system with native k3s support#135
Open
bussyjd wants to merge 6 commits intointegration-okr-1from
Open
feat(stack): pluggable backend system with native k3s support#135bussyjd wants to merge 6 commits intointegration-okr-1from
bussyjd wants to merge 6 commits intointegration-okr-1from
Conversation
Introduce a Backend interface that abstracts cluster lifecycle management, enabling both k3d (Docker-based, default) and k3s (native bare-metal) backends. This is a prerequisite for TEE/Confidential Computing workloads which require direct hardware access that k3d cannot provide. Changes: - Add Backend interface (Init, Up, Down, Destroy, IsRunning, DataDir) - Extract k3d logic into K3dBackend with backward-compatible fallback - Add K3sBackend with sudo process management, PID tracking, and API server readiness checks - Convert helmfile.yaml to helmfile.yaml.gotmpl using env vars instead of .Values references (fixes first-pass template rendering) - Fix eRPC secretEnv type mismatch (map vs string for b64enc) - Fix obol-frontend escaped quotes in gotmpl expressions - Add KUBECONFIG env var to helmfile command for hook compatibility - Add 26 unit tests and 10 integration test scenarios Closes #134
Adds a Claude Code skill (`/test-backend`) with bash scripts that exercise the full backend lifecycle: init, up, kubectl, down, restart, and purge for both k3d and k3s backends.
Update dependency versions to latest stable releases: - kubectl: 1.31.0 → 1.35.0 - helm: 3.19.1 → 3.19.4 - helmfile: 1.2.2 → 1.2.3 - k9s: 0.32.5 → 0.50.18 - helm-diff: 3.9.11 → 3.14.1 k3d remains at 5.8.3 (already current).
Update documentation to reflect the upgraded dependency versions in obolup.sh. This keeps the documentation in sync with the actual pinned versions used by the bootstrap installer.
OisinKyne
reviewed
Feb 9, 2026
Comment on lines
1
to
10
| {{- $network := .Values.network -}} | ||
| {{- $network := env "STACK_NETWORK" | default "mainnet" -}} | ||
| {{- $publicDomain := env "STACK_PUBLIC_DOMAIN" | default "obol.stack" -}} | ||
| {{- $chainId := 1 -}} {{/* Default: mainnet */}} | ||
| {{- if eq $network "hoodi" -}} | ||
| {{- $chainId = 560048 -}} | ||
| {{- else if eq $network "sepolia" -}} | ||
| {{- $chainId = 11155111 -}} | ||
| {{- else if ne $network "mainnet" -}} | ||
| {{- fail (printf "Unknown network: %s. Supported networks: mainnet, hoodi, sepolia" $network) -}} | ||
| {{- end -}} |
Contributor
There was a problem hiding this comment.
Why do we have to chose only one l1? can't we have all of these wired up? (well hoodi and mainnet is what we host on the dv labs side)
OisinKyne
reviewed
Feb 9, 2026
Comment on lines
20
to
21
| - name: stakater | ||
| url: https://stakater.github.io/stakater-charts |
The k3s Down() method was using kill -TERM with a negative PID (process group kill), which could kill unrelated system processes like systemd-logind sharing the same process group as the sudo wrapper. This caused the entire desktop session to crash. Changes: - Kill only the specific sudo/k3s process, not the process group - Remove unused Setpgid/syscall since we no longer use process groups - Add containerd-shim cleanup fallback for binary-only k3s installs - Add 600s helm timeout for kube-prometheus-stack deployment - Disable admission webhook pre-install hooks that timeout on fresh k3s - Fix flaky test: replace fixed sleep with polling loop for API shutdown
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Backendinterface that abstracts cluster lifecycle, enabling both k3d (default) and native k3s backendssecretEnvtype mismatch, obol-frontend escaped quotes,.Values.*unavailable during gotmpl first-pass rendering)What changed
BackendwithInit,Up,Down,Destroy,IsRunning,DataDir— k3d extracted intoK3dBackend, newK3sBackendaddedsudo kill -0liveness checks, process group signals,k3s-killall.shcleanup, API server readiness pollinghelmfile.yaml→helmfile.yaml.gotmpl, env vars replace.Values.*references, KUBECONFIG propagated to hookssecretEnvchanged from nested map to{}, secret injected viaextraEnvwithvalueFrom.secretKeyRef{{ printf \"...\" }}with direct interpolation and single-quotedenvcalls//go:build integrationTest results
-raceTest plan
go test -race ./internal/stack/)stack init --backend k3s→stack up→ full helmfile deploystack down→stack uprestart cyclestack purge --forcefull cleanupCloses #134