Tier A connect console + ADR-0001 (Tier B bastion) - #43
Merged
Conversation
…bastion Tier A: `spero top`'s `s` key now opens a session into any target with the operator's own tools, not just pods. core.shell.connect_argv dispatches on the provider -- kubectl exec for a kubernetes pod, ssh -t for an ssh host, a local shell for a local target -- so `top` is a unified console over the fleet spero already inventories. It brokers nothing and uses no spero-held credentials; access stays bounded by your kubeconfig / ssh config, and it stays local-only. ADR-0001 records the decision on the larger idea: a Tier B brokered bastion that authenticates users and relays recorded sessions into unreachable clusters over the dial-home reverse tunnel. Status: Proposed / not-by-default -- ship Tier A and integrate with an existing access plane (Teleport/Boundary/SSM) unless the reverse-tunnel-into-unreachable-clusters wedge is a deliberate bet, in which case the listed security gates are blocking.
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
1 participant
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.
Tier A — unified connect console (shipped)
spero top'sskey now opens a session into any target with the operator's own tools, not just pods. Newcore.shell.connect_argvdispatches on the provider:k8s:...→kubectl exec -it <pod> -- shssh:[user@]host[:port]→ssh -t [-p port] <dest>local→$SHELLIt brokers nothing and holds no spero credentials — access stays bounded by your kubeconfig / ssh config, and it's local-only (never
--remote/dial-home). Sospero topbecomes a k9s-style console over the mixed host+k8s fleet spero already inventories.Tests:
connect_argvfor ssh (user+port / host-only), local, and k8s-delegates-to-exec. 269 passed, ruff/mypy clean.ADR-0001 — Tier B brokered bastion (decision doc)
adr/0001-tier-b-brokered-bastion.mdrecords the call on the bigger idea: authenticating users and relaying recorded sessions into unreachable clusters over the dial-home reverse tunnel. Status: Proposed / not-by-default — ship Tier A and integrate with an existing access plane (Teleport/Boundary/SSM) unless the reverse-tunnel-into-unreachable-clusters wedge is a deliberate bet, in which case the security gates (per-user OIDC, JIT authz, session recording, no standing creds, bounded agent blast radius) are blocking. (/docs/is gitignored here, so the ADR lives in a tracked top-leveladr/.)