Skip to content
This repository was archived by the owner on Apr 16, 2026. It is now read-only.
This repository was archived by the owner on Apr 16, 2026. It is now read-only.

Create Kubernetes deployment manifests and Helm chart #21

Description

@haasonsaas

Summary

No deployment artifacts exist. Getting ASB into a Kubernetes cluster currently requires hand-rolling manifests.

Required work

  • Helm chart with templates for:
    • Deployment for asb-api (configurable replicas, resource limits, probes)
    • CronJob or Deployment for asb-worker (configurable interval, single-replica)
    • Job for asb-migrate (run-once, pre-upgrade hook)
    • ServiceAccount with appropriate RBAC
    • Service and optional Ingress/IngressRoute
    • ConfigMap for non-secret configuration
    • ExternalSecret or Secret for signing keys, Vault token, GitHub credentials
    • PodDisruptionBudget for API
  • values.yaml with sensible defaults and clear comments
  • HA topology documentation: how many API replicas are safe, what happens if Redis goes down (fall back to in-memory budgets?), Postgres failover behavior
  • Failure mode guide: what happens when each dependency fails, what degrades vs. what goes hard-down
  • Dockerfile (multi-stage build, distroless base, non-root user)
  • CI job to build and push container image with sha-<full_git_sha> tag

Files

  • deploy/helm/asb/ — chart directory
  • Dockerfile — multi-stage build
  • .github/workflows/ — image build and push job

Priority

Low-medium — required for any real deployment but not blocking development.

🤖 Generated with Claude Code

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions