Deployment
48 items tagged with "deployment"
Best Practices5
Blue-Green Deployment Strategy
Operating two identical production environments to achieve zero-downtime releases and quick rollbacks.
Canary Releases Best Practice Guide
Progressively rolling out new software to a small subset of users to minimise risk before full release.
Feature Flag Best Practices
Operational guidelines for creating, managing, and retiring feature toggles safely.
Deployment Rings
A progressive rollout strategy that releases changes to expanding audience groups, or rings, validating each ring before exposing the next to limit blast radius.
Dark Launching
Deploying new functionality to production in a hidden state and exercising it with real traffic before exposing it to users, to validate behavior and capacity safely.
Patterns8
Blue-Green Deployment
Run two identical production environments, switching traffic between them for zero-downtime deployments
Canary Deployment
Gradually roll out changes to a small subset of users before rolling out to the entire infrastructure
Feature Flags
Toggle functionality on or off without deploying new code
Gateway Routing
Routes client requests to the correct backend service through a single endpoint using request attributes such as path or host.
Externalized Configuration
Stores configuration outside the application artifact so the same build runs unchanged across environments.
Geode
Deploy independent geographically distributed nodes that each serve any request, placing compute close to users worldwide.
Deployment Stamps
Deploy multiple independent copies of a full application stack to scale, isolate tenants, and contain failures.
Static Content Hosting
Serve static assets from storage or a CDN instead of application servers to cut load, latency, and cost.
Anti-Patterns5
Manual Deployment
Releasing software through hand-run steps and checklists instead of automation, producing slow, error-prone, irreproducible deploys that depend on individuals.
Monolithic Pipeline
A single, all-or-nothing CI/CD pipeline that builds, tests, and deploys everything together, making it slow, fragile, and hard to change safely.
No Rollback Plan
Deploying with no tested, fast way to revert, so a bad release means scrambling under pressure while the outage drags on.
Deploy and Pray
Pushing releases to production with no automated verification, monitoring, or rollback, then hoping nothing breaks instead of knowing it works.
Latest Tag in Production
Deploying container images by the mutable :latest tag, so production runs an unknown, changing version that cannot be reliably reproduced or rolled back.
Tutorials8
CI/CD Pipeline with GitHub Actions
Set up a complete CI/CD pipeline using GitHub Actions
How to deploy an application to Kubernetes with Deployment and Service
Package an image into a Kubernetes Deployment and expose it with a Service, then scale and roll out updates.
How to package a Kubernetes app with a Helm chart
Create a reusable Helm chart with templated manifests and values so one app deploys cleanly across environments.
How to do blue-green deployments on AWS with CodeDeploy
Run zero-downtime blue-green deployments for containers on Amazon ECS using AWS CodeDeploy and a load balancer.
How to deploy a serverless container with Azure Container Apps
Deploy a containerized service to Azure Container Apps with scale-to-zero, ingress, and revision-based updates.
How to build an environment promotion pipeline
Promote a single build artifact through dev, staging, and production with gated approvals instead of rebuilding per stage.
How to deploy Helm charts to Kubernetes from CI
Package an application as a Helm chart and deploy it to Kubernetes from a CI pipeline with per-environment values.
How to deploy a machine learning model for inference
Serve a trained model behind an HTTP API, containerize it, and scale it for production inference.
Blueprints2
Manual Deployments to Argo CD GitOps Blueprint
Replace manual kubectl and script-based deploys with Argo CD GitOps so Git is the single source of truth for Kubernetes state.
Manual Deployments to Flux GitOps Blueprint
Adopt Flux CD to reconcile Kubernetes clusters from Git, replacing manual deploys with declarative, pull-based GitOps and automated image updates.
Products2
Reference Architectures1
Checklists4
Production Go-Live Readiness Checklist
End-to-end verification that a service is ready to serve real users in production, covering scaling, monitoring, security, and rollback.
GitOps Readiness Checklist
Verify that infrastructure and application delivery follow GitOps principles with Git as the single source of truth and automated reconciliation.
Release & Deployment Cutover Checklist
Coordinate a controlled cutover from an old release or system to a new one, with sequencing, validation, and an explicit abort path.
Rollback Readiness Checklist
Confirm a service can be reverted to a known-good state quickly and safely, covering artifacts, data, configuration, and traffic.
Comparisons2
Helm vs Kustomize
Helm packages Kubernetes apps as templated, versioned charts; Kustomize overlays plain YAML without templates. Helm suits distribution; Kustomize suits simple in-house config.
ArgoCD vs Flux
Argo CD and Flux are the two leading GitOps continuous delivery tools for Kubernetes. Argo CD offers a rich UI; Flux is lightweight and Kubernetes-native by design.
FAQs3
What is CI/CD?
CI/CD stands for Continuous Integration and Continuous Delivery (or Deployment). Continuous Integration means developers merge code into a shared bran...
What is the difference between blue-green and canary deployments?
Both are strategies for releasing new versions with minimal risk. In a blue-green deployment you run two identical environments—one live (blue) and on...
What is a feature flag?
A feature flag (or feature toggle) is a configuration switch that turns functionality on or off at runtime without deploying new code. It lets teams d...
Glossaries6
Feature Flag
A technique allowing features to be enabled or disabled without deploying new code
Deployment (Kubernetes)
A Kubernetes Deployment is a controller that declaratively manages a set of identical pods, handling rollouts, rollbacks, and scaling by maintaining the desired number of replicas.
Continuous Delivery (CD)
A practice where software is kept in a releasable state at all times, with every change automatically built, tested, and prepared for deployment, leaving the final release as a manual decision.
Continuous Deployment
A practice where every change that passes the automated pipeline is released to production automatically, with no manual approval step.
Canary Deployment
A release strategy in which a new version is rolled out to a small subset of users or servers first, so its behavior can be observed before exposing the whole user base.
Error Budget
The maximum amount of unreliability a service is allowed over a period, calculated as the difference between 100% and its service level objective.