feat: add k8s secure deployment references (k3d + aks)#12
Merged
Conversation
Add a k8s/ directory with worked, secure deployment references for the Interbox Helm chart — dashboard behind an internal ingress + TLS + SSO (the dashboard has no built-in auth): - k8s/k3d/ — a runnable, one-command reference on k3d: ingress-nginx + cert-manager (internal CA) + oauth2-proxy + Dex + Interbox + Postgres. Secrets are generated at deploy time (nothing sensitive committed). Verified end-to-end via deploy.sh — the SSO gate (302 to login) and cert-manager TLS both confirmed. - k8s/aks/ — production templates for AKS: internal LB, cert-manager DNS-01 / internal CA, Entra ID SSO, managed Postgres. Schema-validated against cert-manager + k8s; fill the <placeholders>. Also add a "Deploy on Kubernetes" pointer to the README. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ipasechnikov
force-pushed
the
feat/k8s-secure-deploy-references
branch
from
41669c3 to
7c6f9f9
Compare
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.
Adds a
k8s/directory with worked, secure deployment references for the Interbox chart — dashboard behind an internal ingress + TLS + SSO (the dashboard has no built-in auth).k8s/k3d/— runnable, verifiedOne-command local reference (
deploy.sh): ingress-nginx + cert-manager (internal CA) + oauth2-proxy + Dex + Interbox + Postgres. Secrets generated at deploy time — nothing sensitive committed. Verified end-to-end: the SSO gate (302 → login) and the cert-manager-issued TLS cert were both confirmed against a fresh k3d cluster.k8s/aks/— production templatesAKS-shaped templates: internal Azure LB, cert-manager DNS-01 (primary) / internal CA (alt), Entra ID SSO, managed Postgres. Schema-validated against cert-manager + the k8s API (server dry-run); fill the
<placeholders>. Can't be run end-to-end without a real Azure, so it ships as reviewed templates + a prereqs README.Also
k8s/.See the engine docs' Operations → Securing Dashboard Access for the concepts behind this.
🤖 Generated with Claude Code