pulumi · asafashirov · Apr 16, 2025 · Apr 16, 2025 · Apr 16, 2025
diff --git a/content/blog/announcing-crossguard-preview/index.md b/content/blog/announcing-crossguard-preview/index.md
@@ -1,12 +1,16 @@
 ---
 title: "Announcing CrossGuard Preview"
 date: 2019-12-02
+updated: "2025-04-16"
 meta_desc: "Today we are announcing Pulumi CrossGuard, a Policy as Code solution that enforces custom infrastructure policies, is available for all users to preview."
 meta_image: crossguard.png
 authors: ["erin-krengel"]
 tags: ["policy-as-code", "features", "pulumi-news"]
 ---
 
+> [!INFO]
+> This blog post discusses CrossGuard in "preview" status. CrossGuard is now fully released and integrated into Pulumi. For current information about Pulumi's policy as code capabilities, please refer to the [latest CrossGuard documentation](/docs/using-pulumi/crossguard/).
+
 Over the past few months, we have been hard at work on Pulumi CrossGuard, a Policy as Code solution. Using CrossGuard, you can express flexible business and security rules using code. CrossGuard enables organization administrators to enforce these policies across their organization or just on specific stacks. CrossGuard allows you to verify or enforce custom policies on changes before they are applied to your resources. CrossGuard is 100% open source and available to all users of Pulumi, including the Individual Edition. Advanced organization-wide policy management features are available to Enterprise customers.
 
 <!--more-->

diff --git a/content/blog/announcing-public-preview-update-plans/index.md b/content/blog/announcing-public-preview-update-plans/index.md
@@ -1,6 +1,7 @@
 ---
 title: "Announcing the public preview of Update Plans"
 date: 2022-02-09
+updated: 2025-04-16
 meta_desc: Update Plans enable you to see and confirm the updates that will be made to your infrastructure and then apply those updates at a later time.
 meta_image: update_plans_preview.png
 authors:
@@ -9,6 +10,9 @@ tags:
     - features
 ---
 
+> [!INFO]
+> Update Plans are now generally available and no longer require the `PULUMI_EXPERIMENTAL` environment variable. For the most up-to-date information about using Update Plans, please see the [Update Plans documentation](/docs/cli/commands/pulumi-preview#save-a-plan-file).
+
 Pulumi’s previews are an important part of any workflow where you want to see the changes that will be made to your infrastructure before actually making the changes (with `pulumi up`). However, today there is no guarantee that the `pulumi up` operation will do only what was previewed; if the program, or your infrastructure, changes between the preview and the update, the update might make additional changes to bring your infrastructure back in line with what’s defined in your program. We’ve [heard from many of you](https://github.com/pulumi/pulumi/issues/2318) that you need a strong guarantee about exactly which changes an update will make to your infrastructure, especially in critical and production environments.
 
 <!--more-->

diff --git a/content/blog/announcing-pulumi-0.15-kubernetes-cicd-openstack-and-more/index.md b/content/blog/announcing-pulumi-0.15-kubernetes-cicd-openstack-and-more/index.md
@@ -1,11 +1,14 @@
 ---
 title: "Announcing Pulumi 0.15"
 date: "2018-08-15"
+updated: "2025-04-16"
 meta_desc: "Pulumi can now deploy and manage Kubernetes resources using the same familiar programming model supported for AWS, Azure, and Google Cloud Platform."
 authors: ["luke-hoban"]
 tags: ["features", "continuous-delivery"]
 ---
 
+> [!INFO]
+> This blog post refers to an outdated version of Pulumi (0.15). For current features and capabilities, please refer to the [latest documentation](/docs/) and [current release notes](https://github.com/pulumi/pulumi/releases).
 
 Just over a month ago we publicly launched
 Pulumi, a new cloud native development

diff --git a/content/blog/aws-lambda-provisioned-concurrency-no-cold-starts/index.md b/content/blog/aws-lambda-provisioned-concurrency-no-cold-starts/index.md
@@ -150,15 +150,12 @@ Currently, there are issues with autoscaling based on the metrics, which makes p
 
 ## AWS Pricing
 
-{{% notes type="info" %}}
-The most up-to-date pricing can be found on the [AWS Pricing page](https://aws.amazon.com/pricing/?aws-products-pricing.sort-by=item.additionalFields.productNameLowercase&aws-products-pricing.sort-order=asc&awsf.Free%20Tier%20Type=*all&awsf.tech-category=*all).
-{{% /notes %}}
+> [!INFO]
+> The pricing information in this section is outdated. For the most current AWS Lambda pricing, including Provisioned Concurrency costs, please refer to the [official AWS Lambda pricing page](https://aws.amazon.com/lambda/pricing/).
 
-While hand-crafted Lambda warmers are virtually free, provisioned concurrency can be costly. The new pricing is an integral part of the change: Instead of purely per-call model, AWS charges per hour for provisioned capacity.
+While hand-crafted Lambda warmers are virtually free, provisioned concurrency can be costly. The pricing model for Provisioned Concurrency differs from the standard on-demand Lambda model: Instead of purely per-call billing, AWS charges per hour for provisioned capacity.
 
-You would pay $0.015 per hour per GB of provisioned worker memory, even if a worker handled zero requests.
-
-The per-invocation price gets a discount: $0.035 per GB-hour instead of the regular $0.06 per GB-hour. This change means that fully-utilized workers would be cheaper if provisioned compared to on-demand workers.
+You pay for the Provisioned Concurrency you configure, even if a worker handled zero requests, plus a reduced rate for actual usage of those pre-provisioned instances.
 
 {{< figure src="./pricing.png" caption="Comparison of the cost of a 1GB worker for two billing models" alt="Bar chart comparing the cost of a 1GB AWS Lambda worker under on-demand and provisioned concurrency pricing models" >}}
 

diff --git a/content/blog/dotnet-preview/index.md b/content/blog/dotnet-preview/index.md
@@ -1,6 +1,7 @@
 ---
 title: "Infrastructure as Code with .NET and Pulumi"
 date: 2019-11-13T11:23:04-06:00
+updated: 2025-04-16
 draft: false
 meta_desc: "Pulumi launches supports .NET Core languages for Infrastructure as Code"
 meta_image: "meta.png"
@@ -9,6 +10,9 @@ authors:
 tags:
     - ".NET"
 ---
+
+> [!INFO]
+> This post announces .NET Core in preview, which is now fully supported. Pulumi now supports newer .NET versions beyond .NET Core 3.1 mentioned in this article. For the most up-to-date information about using .NET with Pulumi, please see the [.NET documentation](/docs/languages-sdks/dotnet/).
 With the release of [Pulumi for .NET preview](/blog/pulumi-dotnet-core/), we've open the doors to [infrastructure as code](/what-is/what-is-infrastructure-as-code/) to even more developers and operators. Millions of .NET developers can now use their favorite languages and open source ecosystems to build modern, cloud native applications. We've added support for C#, F#, and Visual Basic. Because .NET Core is available on Windows, Linux, and macOS, you have a choice of platforms to use.
 
 You can create cloud resources by writing Microsoft .NET Core programs to build and deploy cloud resources to a wide variety of clouds, including Azure, AWS, GCP and more.  On Azure, you can manage resources like AKS Clusters, Functions, Azure App Services, Virtual Machines, Cosmos DBs, KeyVaults, and much, much more. Let's take a first look at Pulumi for .NET by deploying an application on Azure.

diff --git a/content/blog/enforcing-different-kinds-of-policies-for-cloud-resources/index.md b/content/blog/enforcing-different-kinds-of-policies-for-cloud-resources/index.md
@@ -1,6 +1,7 @@
 ---
 title: "Enforcing Different Kinds of Policies for Cloud Resources"
 date: 2019-12-19
+updated: 2025-04-16
 meta_desc: "A look at the different types of policies that can be written for Pulumi CrossGuard."
 meta_image: crossguard.png
 authors:
@@ -9,6 +10,9 @@ tags:
     - policy-as-code
 ---
 
+> [!INFO]
+> This post describes an early version of Pulumi CrossGuard (Policy as Code). The API and implementation details may have changed. For the most up-to-date information, please see the [CrossGuard documentation](/docs/using-pulumi/crossguard/).
+
 We recently announced [a new policy as code solution, CrossGuard](/blog/announcing-crossguard-preview/) that validates policies at deployment time. Policies are expressed as code and are used to prevent the creation of out-of-compliance resources. This allows an organization to prevent entire classes of security and reliability defects to ensure infrastructure is following best practices. Because policies are written using full-blown programming languages, it's possible to do interesting things such as [combining IAM Access Analyzer and Pulumi CrossGuard](/blog/aws-iam-access-analyzer-and-crossguard/). In this post, we'll take a closer look at the different types of policies that can be written.
 
 <!--more-->

diff --git a/content/blog/if-you-liked-ksonnet-youll-love-pulumi/index.md b/content/blog/if-you-liked-ksonnet-youll-love-pulumi/index.md
@@ -1,12 +1,16 @@
 ---
 title: "If you liked ksonnet, you'll love Pulumi!"
 date: "2019-02-13"
+updated: 2025-04-16
 meta_desc: "Like ksonnet, Pulumi provides complete access to the raw Kubernetes API, and supports additional features like modules/imports, components, functions, and more."
 meta_image: "kube-update.png"
 authors: ["mike-metral"]
 tags: ["Kubernetes", "cloud-native"]
 ---
 
+> [!INFO]
+> This article references ksonnet, which was deprecated in 2019. For the most up-to-date information on using Pulumi with Kubernetes, see our [Kubernetes documentation](/docs/clouds/kubernetes/).
+
 The Kubernetes landscape is constantly evolving as end users and
 developers search for the right tools, approaches, and abstractions to
 help them manage Cloud Native infrastructure in production.

diff --git a/content/blog/inside-crosswalk-for-kubernetes/index.md b/content/blog/inside-crosswalk-for-kubernetes/index.md
@@ -1,6 +1,7 @@
 ---
 title: "Inside Crosswalk for Kubernetes"
 date: 2019-11-21
+updated: 2025-04-16
 draft: false
 meta_desc: "Crosswalk for Kubernetes is a collection of common patterns of usage for provisioning Kubernetes infrastructure and running containerized applications."
 meta_image: "meta.png"
@@ -13,6 +14,9 @@ tags:
  - google-cloud
 ---
 
+> [!INFO]
+> This post describes an early version of Crosswalk for Kubernetes. Some of the links, examples, and implementation details may have changed. For the most up-to-date information, see the [Pulumi Kubernetes documentation](/docs/clouds/kubernetes/).
+
 Running Kubernetes in production can be challenging. This past year, Pulumi has collected common patterns of usage informed by best practices for provisioning Kubernetes infrastructure and running containerized applications. We call this Pulumi Crosswalk for Kubernetes: a collection of playbooks and libraries to help you to successfully configure, deploy, and manage Kubernetes in a way that works for teams in production.
 
 ## Kubernetes is Vast and Complex

diff --git a/content/blog/pulumi-1-0/index.md b/content/blog/pulumi-1-0/index.md
@@ -4,10 +4,13 @@ authors: ["joe-duffy"]
 tags: ["pulumi-news"]
 meta_desc: "We are excited to announce Pulumi 1.0, a modern infrastructure as code platform that works for any cloud, AWS, Azure, GCP, or Kubernetes included."
 date: "2019-09-05"
-
+updated: "2025-04-16"
 meta_image: "pulumi-1-0.png"
 ---
 
+> [!INFO]
+> This blog post announces Pulumi 1.0, which has been superseded by newer versions. For information about the latest Pulumi release, please refer to the [current documentation](/docs/) and [recent release notes](https://github.com/pulumi/pulumi/releases).
+
 Today we are excited to announce the general availability of Pulumi 1.0. Pulumi is a modern infrastructure as code tool that lets you declare infrastructure using familiar, general-purpose languages, with a SaaS management console for configuring identities, organizations, and related policies. By using familiar languages, developers and operators are able to work better together, sharing and reusing best practices, accomplishing new levels of automation, and unlocking access to ecosystems of existing tools. The 1.0 release is a siginificant milestone for us, our community, and our customers, and signals completeness, stability, and compatibility.
 
 ## What is Pulumi?

diff --git a/content/blog/pulumi-2-0/index.md b/content/blog/pulumi-2-0/index.md
@@ -1,12 +1,16 @@
 ---
 date: "2020-04-21"
+updated: "2025-04-16"
 title: "Announcing Pulumi 2.0, Now with Superpowers"
 authors: ["joe-duffy"]
 tags: ["pulumi-news"]
 meta_desc: "Today we are announcing Pulumi 2.0, a modern infrastructure as code platform with advanced capabilities including new languages, testing, and policy as code."
 meta_image: "pulumi-2-0.png"
 ---
 
+> [!INFO]
+> This blog post announces Pulumi 2.0, which has been superseded by newer versions. For information about the latest Pulumi release, please refer to the [current documentation](/docs/) and [recent release notes](https://github.com/pulumi/pulumi/releases).
+
 Today we are excited to announce Pulumi 2.0, the next major stage in our journey as an open source project, company, and community. This release expands on our original vision of using your favorite languages and tools to do all things infrastructure as code, now with new cloud engineering superpowers that will help you and your team adopt modern cloud architectures.
 
 <!--more-->

diff --git a/content/blog/simplified-outputs-in-pulumi-0.17.0/index.md b/content/blog/simplified-outputs-in-pulumi-0.17.0/index.md
@@ -3,10 +3,14 @@ title: "Simplified Outputs in Pulumi 0.17"
 authors: ["cyrus-najmabadi"]
 tags: ["features"]
 date: "2019-03-19"
+updated: "2025-04-16"
 meta_desc: "Based on feedback from cloud developers, Pulumi Outputs have been simplified for JavaScript and TypeScript simplifying the user experience."
 meta_image: "comp-list.png"
 ---
 
+> [!INFO]
+> This blog post refers to an outdated version of Pulumi (0.17). For current information about Outputs and the latest features, please refer to the [Inputs and Outputs documentation](/docs/concepts/inputs-outputs/).
+
 Pulumi allows cloud developers to use programming languages like
 JavaScript, TypeScript and Python to define and deploy cloud
 infrastructure and applications. To do this, Pulumi exposes a notion of