Application Templates
In Development
This feature is currently in development. Template catalog described here is subject to change.
Purpose: For platform engineers and app developers, describes application templates — pre-built deployment patterns that teams instantiate to get running quickly with best-practice configurations.
What Are Templates
Templates are opinionated, platform-team-curated application scaffolds that include:
- Kubernetes manifests (Deployment, Service, Ingress/HTTPRoute)
- CI/CD pipeline configuration
- Observability wiring (ServiceMonitor, log labels, trace propagation)
- Security defaults (NetworkPolicy, PodSecurityContext)
- GitOps structure (Kustomize base + overlay per environment)
Template Catalog
| Template | Stack | Includes |
|---|---|---|
web-service | HTTP API (any language) | Deployment, HTTPRoute, HPA, ServiceMonitor |
worker | Background processor | Deployment, PDB, resource limits |
cronjob | Scheduled task | CronJob, RBAC, failure alerting |
stateful-app | App with database | StatefulSet, PVC, backup CronJob |
event-consumer | Kafka consumer | Deployment, KEDA ScaledObject, DLQ topic |
Template Parameters
When instantiating a template, teams provide:
| Parameter | Example | Purpose |
|---|---|---|
appName | payment-api | Resource naming |
team | checkout | Namespace and RBAC scoping |
environment | staging | Overlay selection |
replicas | 3 | Initial scale |
image | harbor.internal/checkout/payment-api | Container image |
How It Works
- Team selects template from portal UI
- Fills in parameters
- Portal generates Kustomize overlay from template + parameters
- Commits to team's GitOps repository
- FluxCD reconciles — app deployed with full observability and security