Protecting Your Production

At Prodvana, we believe that production environments should be protected, and policies safeguarding them should be codified into your release process. This month, we have made several improvements to give you more power and control over how to protect your production environments.

• Approvals are supercharged. You can require approvals from multiple distinct users and ensure that they are never skipped, even in a rollback.

• Protections can now prevent deployments even in the deployment lifecycle. Previously, Protections could only be defined before a Service Instance entered the deployment lifecycle, which meant that if the Service Instance entered the lifecycle and the Protection failed later, it would not prevent future deployments. You can now define Protections that will be checked every time Prodvana goes to take an action.

• Protections and Release Channel dependencies can now be bypassed in an emergency with a single click.

With these improvements, you can rest easy knowing that your production environments are safe as you continue to deploy and deliver value to your business.

Misc

• For users of Custom Runtimes, you can now define a concurrency limit to control how many Service Instances are running apply at once.

• Container registry integrations can now be configured via Terraform and Pulumi.

• We shipped a new UI to show where you are in the deployment of a Service Instance and, for users of Custom Runtimes, what fetch and apply jobs are running and how they relate to each other.

• RBAC roles can now be mapped from Okta.

• You can now define dependencies between Convergence Extensions.

• You can now dedup Convergence Extensions based on template variables.

• Fixed a bug with viewing historical releases where some actions would still show as ongoing or converging.

• Fixed a bug with retry behavior for Convergence Extension and Custom Runtime applies.

• We made several performance improvements across the board so that you can scale to hundreds of Release Channels.

Revamped Slack Notifications

Our users love Slack! We are excited to announce the next iteration of our Slack application. Notifications now contain helpful, contextual information about releases. They are also threaded and live updated, so you can see your release history and status at a glance without leaving Slack.

See our docs for instructions on how to set up Slack.

Deeper Helm Integration

Our Helm integration has been supercharged. Kubernetes objects managed by Helm are displayed as well as what version each resource is on, so you know which object to look at when a deployment is installed.

New Service Instance Page

Ever want to understand what is going on with a Service in production without having to go through a bunch of releases that never made it to production? We have a new page that focuses on just the Service Instance, so you can see at a glance everything that has been happening.

Misc/Bug Fixes

• A new builtin protection, Allowed Times, can be used to prevent deployments during off hours or maintenance windows.

• The Service bundle name can now be customized, e.g. if you want to use a semantic version string.

• Added a search bar to the Service convergence page to quickly find the Service Instance you are looking for.

• Added a version summary pie chart to the Service page to see what's live.

• AI integrations can now be turned off in the new organization settings page.

• Prodvana Agent can now operate with a minimal set of permissions. You can choose to lock down what namespaces it can access and what resource types.

• Published new examples for Terraform and tenancy.

• Fixed a bug with deployment logging on Custom Runtimes when every action approval is turned on.

• Fixed an issue where high-impact commits would never be analyzed when there are too many commits in between deployments.

Blue/Green Deployments

We are excited to announce support for blue/green deployments via Argo Rollouts. Blue/green deployment is a deployment strategy where the new version of the Service is spun up identically to the old version, with traffic being shifted to the new version. With blue/green deployments, Service owners can roll out changes with more granular control and validation.

Argo Rollouts power blue/green deployments. Create a Rollout object with bluegreen strategy and Prodvana will track and display progress for the deployment in the web UI. The UI also supports pausing/unpausing (approvals) and aborts.

To get started with blue/green deployments, see our documentation.

Misc/Bug Fixes

• Our Service convergence UI will now indicate when a convergence is blocked by a Protection.

• Enhanced our AWS ECS authentication model to be role-based instead of relying on a static set of credentials.

• Added support for parametrization of non-string variables like replica count on Kustomize (and other templating engines with a strict type system) via patching.

• Show kubectl apply errors on the convergence sidebar.

• Added a page to show Application configurations.

• Added structured output mode for Custom Runtime fetches, allowing Custom Runtime owners to return the list of active versions with replica count. This gives service owners the same experience with Custom Runtimes as with Kubernetes Runtimes.

• Fixed timeouts on pvnctl configs apply that were impacting customers with a large number of Release Channels.

• Made Prodvana Agent more resilient to single-host failures on user clusters.

• Changed default retry policy for Convergence Extension to not retry on failure. Retries can now be configured to retry a limited number of times or forever (previous behavior was retry forever).

Maestro: An Intelligent Conductor for Releases

We're excited to announce the launch of Maestro, an intelligent layer atop Prodvana’s Managed Delivery. Designed to sequence complex releases, Maestro is like a conductor who knows every note of the symphony and perfectly times each section's entrance. 

While Prodvana’s Managed Delivery already excels at rolling out a single release safely and efficiently across all your Release Channels, Maestro enables you to sequence multiple releases before any one of them fully completes. Maestro is perfect for deploying each commit separately for testing or managing week-long deployments of stateful systems.

More information about Maestro can be found in our blog. To get started with Maestro, see our documentation.

Misc/Bug Fixes

• Revamped our web UI to be more consistent and accessible.

• Added a universal search bar.

• Added roles-based access control (RBAC), allowing you to safeguard your production while still giving everyone visibility into what is running.

• Added support for Amazon ECS and Google Cloud Run.

• Fixed pagination on Release History page.

• Show commits removed (e.g. rollbacks) as part of a release in addition to commits being added.

• Improved authentication handling in pvnctl.

• Protections can now be tied to the convergence itself, allowing protections on incoming changes, e.g. to prevent a change from going out before database migrations were run.

• Allow autorollback to be disabled at a Runtime level.

• Added commit denylist as a builtin protection.

• Added pvnctl preflight to diagnose incoming Runtimes for issues.