> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/3.0/use-deployments.md).

# Use Deployments

- [Kubernetes](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes.md)
- [Overview](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/overview.md): Deploy container images to a Kubernetes cluster using Harness CD.
- [Kubernetes services](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/kubernetes-services.md): Configure Kubernetes services in Harness, manifests, artifact sources, override files, and sidecars.
- [Kubernetes infrastructure](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/kubernetes-infrastructure.md): Create Harness environments and Kubernetes infrastructure definitions to target your cluster for deployment.
- [Deployment Strategies](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/kubernetes-deployment-strategies.md)
- [Kubernetes rolling deployment](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/kubernetes-deployment-strategies/rolling.md): Deploy a new version to all pods incrementally using a rolling update, with automatic rollback on failure.
- [Kubernetes canary deployment](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/kubernetes-deployment-strategies/canary.md): Deploy a canary version of your application alongside the stable version, validate it, then promote with a full rolling deploy.
- [Kubernetes blue-green deployment](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/kubernetes-deployment-strategies/blue-green.md): Deploy a new version to a stage environment, validate it, then swap service selectors to route production traffic to the new version.
- [Blank canvas Kubernetes deployment](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/kubernetes-deployment-strategies/blank-canvas.md): Build a Kubernetes stage from scratch using the Apply step, without a managed rolling, canary, or blue-green strategy.
- [Step Library](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library.md)
- [Kubernetes Apply](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-apply.md): Apply Kubernetes manifests directly to the cluster without using a managed release strategy.
- [Kubernetes Canary Deploy](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-canary-deploy.md): Deploy a subset of pods with the new version alongside the stable version for validation before a full rollout.
- [Kubernetes Blue Green Swap Services Selectors](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-blue-green-swap-services.md): Switch Kubernetes service selectors to route production traffic to the new pod set after a blue-green deploy.
- [Kubernetes Rolling Deploy](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-rolling-deploy.md): Prepare manifests, apply them to the cluster, and wait for all pods to reach steady state.
- [Kubernetes Delete](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-delete.md): Delete Kubernetes resources by name, manifest path, or release name.
- [Kubernetes Steady State Check](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-steady-state-check.md): Wait for Kubernetes workloads to reach a healthy running state after a deployment or scale operation.
- [Kubernetes Rolling Rollback](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-rolling-rollback.md): Re-apply the previous release manifests to roll back a failed rolling or canary deployment.
- [Kubernetes Diff](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-diff.md): Compare the current state of the cluster with the desired state defined in your manifests.
- [Kubernetes Traffic Shift step](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-traffic-shift.md): Shift traffic between service versions using Istio VirtualServices or Kubernetes Gateway API HTTPRoutes.
- [Kubernetes Scale](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-scale.md): Scale a Kubernetes workload to a specific number of instances or a percentage of current instances.
- [Kubernetes Blue Green Deploy](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-blue-green-deploy.md): Deploy the new version to the stage pod set and wait for it to reach steady state before a traffic swap.
- [Kubernetes Patch](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-patch.md): Modify a specific Kubernetes workload in place without redeploying the full manifest.
- [Kubernetes Dry Run](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-dry-run.md): Validate Kubernetes manifests against the cluster without applying changes.
- [Kubernetes Rollout](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-rollout.md): Run kubectl rollout subcommands against Kubernetes workloads identified by name, manifest path, or release name.
- [Kubernetes Canary Delete](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-canary-delete.md): Remove the canary workload after validation or on rollback.
- [Kubernetes Blue Green Stage Scale Down](https://developer.harness.io/continuous-delivery/3.0/use-deployments/kubernetes/step-library/k8s-blue-green-stage-scale-down.md): Clean up the old pod set after a successful blue-green swap to free cluster resources.
- [Helm](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm.md)
- [Overview](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/overview.md): Deploy Helm charts to a Kubernetes cluster using Harness CD.
- [Helm services](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/helm-services.md): Configure Helm services in Harness: chart sources, values files, artifact sources, sidecars, and advanced options.
- [Helm infrastructure](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/helm-infrastructure.md): Create Harness environments and Native Helm infrastructure definitions to target your cluster for Helm deployments.
- [Deployment Strategies](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/helm-deployment-strategies.md)
- [Helm basic deployment](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/helm-deployment-strategies/basic.md): Deploy a Helm chart to all instances in a single phase using helm upgrade --install.
- [Helm canary deployment](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/helm-deployment-strategies/canary.md): Deploy a Helm chart to a subset of instances using a separate canary release, validate, then promote to full deployment.
- [Helm blue-green deployment](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/helm-deployment-strategies/blue-green.md): Deploy a Helm chart to a stage service alongside the primary release, then swap traffic between them.
- [Blank canvas Helm deployment](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/helm-deployment-strategies/blank-canvas.md): Build a Helm stage from scratch using the Helm Basic Deploy step, without a managed canary or blue-green strategy.
- [Step Library](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/step-library.md)
- [Helm Basic Deploy](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/step-library/helm-basic-deploy.md): Run helm upgrade --install against the target cluster and wait for all workloads to reach steady state.
- [Helm Canary Deploy](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/step-library/helm-canary-deploy.md): Install a separate canary Helm release alongside the stable release with a controlled instance count or percentage.
- [Helm Canary Delete](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/step-library/helm-canary-delete.md): Uninstall the canary Helm release after validation or on rollback.
- [Helm Blue Green Deploy](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/step-library/helm-blue-green-deploy.md): Deploy the new chart version to the stage service and wait for it to reach steady state before a traffic swap.
- [Helm Blue Green Swap](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/step-library/helm-blue-green-swap.md): Switch service selectors to route production traffic to the new workload after a blue-green deploy.
- [Helm Rollback](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/step-library/helm-rollback.md): Revert a Helm release to a previous revision after a failed deployment.
- [Helm Delete](https://developer.harness.io/continuous-delivery/3.0/use-deployments/helm/step-library/helm-delete.md): Uninstall a Helm release and remove all associated Kubernetes resources from the cluster.
- [Serverless](https://developer.harness.io/continuous-delivery/3.0/use-deployments/serverless.md)
- [Overview](https://developer.harness.io/continuous-delivery/3.0/use-deployments/serverless/overview.md): Deploy AWS Lambda functions using the Serverless Framework with Harness CD.
- [Serverless services](https://developer.harness.io/continuous-delivery/3.0/use-deployments/serverless/serverless-services.md): Configure Serverless Lambda services in Harness, including manifest sources, artifact sources, and expression handling.
- [Serverless infrastructure](https://developer.harness.io/continuous-delivery/3.0/use-deployments/serverless/serverless-infrastructure.md): Create Harness environments and Serverless Lambda infrastructure definitions to target your AWS account for deployment.
- [Serverless deployment](https://developer.harness.io/continuous-delivery/3.0/use-deployments/serverless/serverless-deployment.md): Configure and run Serverless Lambda deployments in Harness, including containerized steps, rollback, and framework version support.
- [Step Library](https://developer.harness.io/continuous-delivery/3.0/use-deployments/serverless/step-library.md)
- [Serverless Package](https://developer.harness.io/continuous-delivery/3.0/use-deployments/serverless/step-library/serverless-package.md): Bundle Lambda functions and prepare the CloudFormation deployment package using the Serverless Framework package command.
- [Serverless Deploy](https://developer.harness.io/continuous-delivery/3.0/use-deployments/serverless/step-library/serverless-deploy.md): Deploy a Serverless Lambda service to AWS using the Serverless Framework deploy command.
- [Serverless Rollback](https://developer.harness.io/continuous-delivery/3.0/use-deployments/serverless/step-library/serverless-rollback.md): Restore a Serverless Lambda CloudFormation stack to its previous state when a deployment fails.
- [Google Cloud Run](https://developer.harness.io/continuous-delivery/3.0/use-deployments/google-cloud-run.md)
- [Overview](https://developer.harness.io/continuous-delivery/3.0/use-deployments/google-cloud-run/overview.md): Deploy containerized applications to Google Cloud Run using Harness CD.
- [Google Cloud Run services](https://developer.harness.io/continuous-delivery/3.0/use-deployments/google-cloud-run/google-cloud-run-services.md): Define a Harness service for Google Cloud Run deployments, including the service manifest and artifact source.
- [Google Cloud Run infrastructure](https://developer.harness.io/continuous-delivery/3.0/use-deployments/google-cloud-run/google-cloud-run-infrastructure.md): Create Harness environments and Google Cloud Run infrastructure definitions to target your GCP project for deployment.
- [Deployment Strategies](https://developer.harness.io/continuous-delivery/3.0/use-deployments/google-cloud-run/google-cloud-run-deployment-strategies.md)
- [Basic deployment](https://developer.harness.io/continuous-delivery/3.0/use-deployments/google-cloud-run/google-cloud-run-deployment-strategies/basic.md): Deploy a new Cloud Run revision and route all traffic to it immediately using the Basic deployment strategy.
- [Canary deployment](https://developer.harness.io/continuous-delivery/3.0/use-deployments/google-cloud-run/google-cloud-run-deployment-strategies/canary.md): Deploy a new Cloud Run revision, shift traffic gradually, then promote using the Canary deployment strategy.
- [Blank canvas deployment](https://developer.harness.io/continuous-delivery/3.0/use-deployments/google-cloud-run/google-cloud-run-deployment-strategies/blank-canvas.md): Build a Google Cloud Run stage from scratch without a managed Basic or Canary strategy.
- [Step Library](https://developer.harness.io/continuous-delivery/3.0/use-deployments/google-cloud-run/step-library.md)
- [Google Cloud Run Deploy](https://developer.harness.io/continuous-delivery/3.0/use-deployments/google-cloud-run/step-library/gcr-deploy.md): Apply a Cloud Run service manifest and create a new revision using the Google Cloud Run Deploy step.
- [Google Cloud Run Traffic Shift](https://developer.harness.io/continuous-delivery/3.0/use-deployments/google-cloud-run/step-library/gcr-traffic-shift.md): Route traffic to a specific Cloud Run revision using the Google Cloud Run Traffic Shift step.
- [Google Cloud Run Rollback](https://developer.harness.io/continuous-delivery/3.0/use-deployments/google-cloud-run/step-library/gcr-rollback.md): Restore the previous Cloud Run traffic distribution after a failed deployment using the Google Cloud Run Rollback step.
- [Google Cloud Run Job](https://developer.harness.io/continuous-delivery/3.0/use-deployments/google-cloud-run/step-library/gcr-job.md): Deploy and execute a Cloud Run Job using the Google Cloud Run Job step.
- [AWS Lambda](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-lambda.md)
- [Overview](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-lambda/overview.md): Deploy AWS Lambda functions using Harness CD.
- [Lambda services](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-lambda/lambda-services.md): Configure AWS Lambda services in Harness — function definitions, alias definitions, and artifact sources.
- [Lambda infrastructure](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-lambda/lambda-infrastructure.md): Create Harness environments and AWS Lambda infrastructure definitions to target your AWS account and region for deployment.
- [Deployment Strategies](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-lambda/lambda-deployment-strategies.md)
- [Lambda canary deployment](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-lambda/lambda-deployment-strategies/canary.md): Gradually shift traffic to a new Lambda function version using weighted aliases, then promote fully once validated.
- [Lambda rolling deployment](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-lambda/lambda-deployment-strategies/rolling.md): Deploy a new Lambda function version and shift all traffic to it immediately using a basic rolling strategy.
- [Step Library](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-lambda/step-library.md)
- [AWS Lambda Canary Deploy](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-lambda/step-library/lambda-canary-deploy.md): Publish a new Lambda function version and create a weighted alias to begin routing canary traffic alongside the stable version.
- [AWS Lambda Traffic Shift](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-lambda/step-library/lambda-traffic-shift.md): Route a percentage of Lambda function traffic to a new version via a weighted alias.
- [AWS Lambda Canary Rollback](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-lambda/step-library/lambda-canary-rollback.md): Reset a Lambda function alias to route all traffic back to the previous version after a failed canary deployment.
- [AWS Lambda Rolling Deploy](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-lambda/step-library/lambda-rolling-deploy.md): Publish a new Lambda function version and immediately route all traffic to it using a rolling update strategy.
- [AWS Lambda Rolling Rollback](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-lambda/step-library/lambda-rolling-rollback.md): Restore a Lambda function to its previous version after a failed rolling deployment.
- [AWS SAM](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-sam.md)
- [Overview](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-sam/overview.md): Set up an AWS SAM deployment pipeline in Harness: configure the Deploy stage, select a runtime, and understand the three steps Harness adds automatically.
- [SAM services](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-sam/sam-services.md): Configure AWS SAM services in Harness: SAM directory manifests, values.yaml Go templating, and service variables.
- [SAM infrastructure](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-sam/sam-infrastructure.md): Create Harness environments and AWS SAM infrastructure definitions to target your AWS account and region for SAM deployments.
- [AWS SAM Deploy](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-sam/aws-sam-deploy.md): Configure and run an AWS SAM deployment in Harness: three auto-added steps, how to configure each one, and what happens during execution.
- [Docker in Docker](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-sam/docker-in-docker.md): Reference for the Docker in Docker background step — starts a Docker daemon inside the pod so SAM Build can run container-based builds.
- [SAM Build](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-sam/sam-build.md): Reference for the AWS SAM Build step — builds an AWS SAM application inside a Lambda-compatible container using sam build.
- [SAM Deploy](https://developer.harness.io/continuous-delivery/3.0/use-deployments/aws-sam/sam-deploy.md): Reference for the AWS SAM Deploy step — packages and deploys an AWS SAM application to a CloudFormation stack using sam deploy.