The Deployment Pipeline
When you deploy an application on Boottify, a multi-step automated pipeline handles everything from building your code to making it accessible on the web.
Pipeline Stages
- Image Build — Your application is packaged into a Docker container image using the template's Dockerfile or a custom build configuration.
- Registry Push — The built image is pushed to the platform's private container registry.
- Namespace Provisioning — A dedicated Kubernetes namespace is created for your application with resource quotas matching your plan.
- Container Deployment — The container is deployed as a Kubernetes deployment with the specified replicas, environment variables, and resource limits.
- DNS Configuration — DNS records are created for your subdomain, pointing to the cluster's ingress controller.
- SSL Issuance — An SSL certificate is automatically issued via Let's Encrypt, enabling HTTPS.
Monitoring Deployment
Track your deployment progress in real-time:
- The Deployment tab shows each stage with pass/fail status.
- Build Logs display the Docker build output line by line.
- Deployment Logs show Kubernetes events and container startup output.
- A webhook notification is sent when deployment completes (if configured).
Redeployment
To redeploy an existing application:
- Navigate to the application detail page.
- Click Redeploy to trigger a fresh build and deployment.
- The previous version continues running until the new deployment is healthy (zero-downtime).
Resource Limits
Each plan defines resource limits that are enforced by Kubernetes:
- CPU — Processing power allocated to your container.
- Memory — RAM available for your application.
- Storage — Persistent disk space for data.
- Exceeding limits may cause throttling (CPU) or OOM termination (memory).