1. Docs
  2. Administration
  3. Self-Hosting
  4. Operations
  5. Upgrades

Upgrade Pipeline

    Self-hosting is only available with Pulumi Business Critical. If you would like to evaluate the self-hosted Pulumi Cloud, sign up for the 30-day trial or contact us.

    This page covers how to safely update your self-hosted Pulumi Cloud deployment. For version-specific changes, see the Changelog.

    Staged rollouts

    Deploy updates through staged environments:

    1. Staging/testing - Deploy and run automated tests.
    2. Production - Deploy after staging validation.

    Update process

    Many customers use the self-hosted installers as reference architectures and build their own deployment pipelines. The guidance below applies whether you use the installers directly or your own automation.

    Self-hosted deployments have three logical layers, which should be updated in order:

    1. Infrastructure layer (network, database, storage) - rarely changes
    2. Compute layer (Kubernetes cluster, ECS cluster) - occasional updates
    3. Application layer (API service, console, migrations) - most frequent updates

    For application updates:

    1. Update the container image tag to the new version.
    2. Run database migrations before updating service containers.
    3. Roll out new containers with zero downtime.

    Version pinning

    • Pin the imageTag to a specific version rather than using latest.
    • Available tags are published at Docker Hub: pulumi/service.
    • Test new versions in a staging environment before promoting to production.