Summary

Provision and configure a single-node k3s Kubernetes cluster on Oracle Cloud Infrastructure (OCI) to serve as the staging environment for Sztab.

This staging environment will support:

• Deployment of release images via Helm
• Validation of Docker → Kubernetes migration
• Ingress and networking validation
• Database migration testing (Flyway)
• Pre-production smoke testing

Objective

Create a reproducible staging environment running:

• sztab-backend (Spring Boot)
• sztab-ui (Nginx static build)
• sztabina (embedded Git service)
• Postgres (in-cluster StatefulSet)
• Traefik ingress (default from k3s)

All components deployed within namespace: sztab-staging.

Scope

1. Provision OCI VM (Ubuntu 22.04)
2. Install and configure k3s (single-node cluster)
3. Configure remote kubectl access
4. Create namespace sztab-staging
5. Push release images to OCI Container Registry
6. Configure imagePullSecrets for registry access
7. Deploy Sztab components via Helm
8. Configure ingress (Traefik)
9. Validate full deployment
10. Document deployment and upgrade procedure

Out of Scope

• Multi-node HA cluster
• Autoscaling
• Production-grade database HA
• Regional failover
• Observability stack (Prometheus/Grafana/ELK)
• CI/CD automation (future task)

Deliverables

• Running k3s cluster on OCI VM
• Namespace sztab-staging
• Helm-based deployment working end-to-end
• Public staging endpoint (HTTP or HTTPS)
• Deployment documentation committed to repository
• Verified successful startup of all components

Acceptance Criteria

• kubectl get nodes shows node in Ready state
• All pods in sztab-staging namespace Running and Ready
• Ingress responds successfully
• Backend /actuator/health reports UP
• Postgres PVC bound and stable
• Deployment reproducible using Helm upgrade/install

Notes

This task establishes a stable staging foundation for future releases and enables controlled pre-production validation of Sztab.