pulumi · CamSoper · Jul 27, 2026 · Jul 25, 2026
diff --git a/content/blog/announcing-per-user-pricing-and-unlimited-stacks-for-teams/index.md b/content/blog/announcing-per-user-pricing-and-unlimited-stacks-for-teams/index.md
@@ -7,6 +7,7 @@ authors: ["joe-duffy"]
 tags:
   - features
 category: product
+faq_schema: true
 ---
 
 {{% notes type="warning" %}}

diff --git a/content/blog/aws-lambda-container-support/index.md b/content/blog/aws-lambda-container-support/index.md
@@ -14,6 +14,7 @@ tags:
     - containers
     - serverless
 category: tutorials
+faq_schema: true
 ---
 
 **TL;DR** &mdash; To run a container image in AWS Lambda, build an OCI image that implements the [Lambda Runtime API](https://docs.aws.amazon.com/lambda/latest/dg/runtimes-api.html) (most teams start from an [AWS-provided base image](https://gallery.ecr.aws/lambda/)), push it to Amazon ECR, and create a Lambda function with `packageType: "Image"` pointing at the image URI. Lambda containers support images up to 10&nbsp;GB, up to 10&nbsp;GB of memory, up to 10&nbsp;GB of `/tmp` ephemeral storage, and a 15-minute execution ceiling. Pulumi automates the build, push, and function wiring in a single program. Pick Lambda containers when your workload is event-driven and bursty but your dependencies (binaries, ML models, system libraries) outgrow the 250&nbsp;MB ZIP limit; pick [AWS Fargate or ECS](/docs/iac/guides/clouds/aws/) when you need long-running tasks, persistent connections, or multi-container pods.

diff --git a/content/blog/azure-container-solutions/index.md b/content/blog/azure-container-solutions/index.md
@@ -10,6 +10,7 @@ tags:
     - azure
     - containers
 category: general
+faq_schema: true
 ---
 
 Containers have emerged as one of the de facto standards for running software. When adopted with the right mindset, they can drastically improve the development lifecycle and help to close the loop between local development and running your applications in the cloud.

diff --git a/...ge-vs-pulumi-idp-why-infrastructure-first-platform-engineering-matters/index.md b/...ge-vs-pulumi-idp-why-infrastructure-first-platform-engineering-matters/index.md
@@ -41,6 +41,7 @@ social:
         Read my full analysis of why infrastructure-first platform engineering delivers better outcomes.
 
         #PlatformEngineering #Backstage #Pulumi #InfrastructureAsCode #DevOps #CloudNative #InternalDeveloperPlatform
+faq_schema: true
 ---
 
 Developers are losing days every month to infrastructure bottlenecks, compliance hurdles, and inconsistent environments.

diff --git a/content/blog/developer-experience-business-critical/index.md b/content/blog/developer-experience-business-critical/index.md
@@ -15,6 +15,7 @@ tags:
 category: general
 aliases:
     - /blog/software-developer-experience-devex-devx-devops-culture
+faq_schema: true
 ---
 
 "Developer experience is hard to sell," said Cleve Littlefield, Engineering Manager at Pulumi, during a casual meeting. With experience as both an end-user developer and a lead in self-service platform implementation, Cleve's observation stuck with me.

diff --git a/content/blog/embrace-kubernetes-part1/index.md b/content/blog/embrace-kubernetes-part1/index.md
@@ -9,6 +9,7 @@ tags:
     - kubernetes
 category: best-practices
 series: embrace-kubernetes
+faq_schema: true
 ---
 
 When you’re considering whether or not to implement Kubernetes, perhaps the first question to ask yourself is do you need it at all?

diff --git a/content/blog/fast-docker-image-builds-with-pulumi/index.md b/content/blog/fast-docker-image-builds-with-pulumi/index.md
@@ -14,6 +14,7 @@ tags:
     - providers
     - features
 category: best-practices
+faq_schema: true
 ---
 
 **How do I speed up Docker image builds with Pulumi?** Use [BuildKit](https://docs.docker.com/build/buildkit/) (the default since Docker 23), enable a registry or layer cache so repeated builds reuse work, write a multi-stage Dockerfile so production images skip build-time dependencies, and reach for the dedicated [Docker Build provider](/registry/packages/docker-build/) when you need buildx features like multi-platform images, build secrets, or Docker Build Cloud. With these techniques together, repeat builds in a Pulumi program commonly drop from minutes to seconds.

diff --git a/content/blog/generative-ai-apps-devops-talks-pulumi-user-group/index.md b/content/blog/generative-ai-apps-devops-talks-pulumi-user-group/index.md
@@ -14,6 +14,7 @@ tags:
    - langchain
    - ml
 category: community
+faq_schema: true
 ---
 
 The emergence of DevOps revolutionized software development. Now, with AI powered tools like LangChain, these transformations are being accelerated. Unsurprisingly, our distinguished speaker at the launch of Pulumi's in-person AI Talks, Patrick Debois, who coined the term "DevOps," has recently tuned into LLM and GenAI Ops using the Langchain framework.

diff --git a/content/blog/helm-release-resource-for-kubernetes-generally-available/index.md b/content/blog/helm-release-resource-for-kubernetes-generally-available/index.md
@@ -36,6 +36,7 @@ category: product
 
 # See the blogging docs at https://github.com/pulumi/docs/blob/master/BLOGGING.md.
 # for additional details, and please remove these comments before submitting for review.
+faq_schema: true
 ---
 
 Back in September 2021 we announced [public preview](/blog/full-access-to-helm-features-through-new-helm-release-resource-for-kubernetes/) for the Helm Release resource in Pulumi's Kubernetes provider. Over the last few months, we have had a very encouraging uptake in usage and several meaningful discussions with users in the community that have helped shape improvements to this resource. Thanks to this collaboration, we are now pleased to announce that the [Helm Release](/registry/packages/kubernetes/api-docs/helm/v3/release/) resource is now **GA** (generally available) starting in [v3.15.0](https://github.com/pulumi/pulumi-kubernetes/releases/tag/v3.15.0) of the Pulumi Kubernetes Provider and SDK in all Pulumi supported languages. We are excited to offer yet another tool to Pulumi users to effectively manage their Kubernetes footprint.

diff --git a/content/blog/kubernetes-best-practices-i-wish-i-had-known-before/index.md b/content/blog/kubernetes-best-practices-i-wish-i-had-known-before/index.md
@@ -27,6 +27,7 @@ social:
 
     Whether you're just starting or looking to refine your Kubernetes setup, these insights will help you navigate the complexities and harness the full power of Kubernetes.
     <link>
+faq_schema: true
 ---
 
 **Kubernetes best practices** are the production-tested rules that keep clusters reliable, secure, and affordable: set resource requests and limits on every container, isolate workloads with namespaces and NetworkPolicies, enforce least-privilege RBAC, automate health checks, ship via GitOps, validate every change with policy-as-code, generate an SBOM for every image, and manage Kubernetes itself with infrastructure as code instead of hand-rolled YAML. The 20 practices below cover what production teams actually do in 2026 — not what tutorials suggest.

diff --git a/content/blog/run-deepseek-on-aws-ec2-using-pulumi/index.md b/content/blog/run-deepseek-on-aws-ec2-using-pulumi/index.md
@@ -39,6 +39,7 @@ social:
         OpenAI-compatible API access from your existing tooling
 
     Read the full guide: <link>
+faq_schema: true
 ---
 
 <script type="application/ld+json">

diff --git a/content/blog/serverless-api/index.md b/content/blog/serverless-api/index.md
@@ -43,6 +43,7 @@ social:
             40,000 requests/month
             Typical cost: ~$0.04/month (worst-case ~$1.12/month)
             Zero traffic = Zero cost
+faq_schema: true
 ---
 
 **TL;DR (2026 pricing):** Packaging a Flask app as a container and running it on AWS Lambda behind an HTTP API Gateway costs **~$1.12/month** worst-case, or **$0 when idle**. The breakdown: $0.04 for API Gateway requests, $0.07 for Lambda compute (fully absorbed by the always-free tier), and $1.08 for 12 GB of egress at $0.09/GB (covered by AWS's 100 GB/month free egress allowance unless other services in the account have already used it). Pulumi handles the entire infrastructure. Verified against AWS pricing as of April 2026.

diff --git a/content/blog/the-guide-platform-engineering-idp-steps-best-practices/index.md b/content/blog/the-guide-platform-engineering-idp-steps-best-practices/index.md
@@ -58,6 +58,7 @@ social:
 
 # See the blogging docs at https://github.com/pulumi/docs/blob/master/BLOGGING.md
 # for details, and please remove these comments before submitting for review.
+faq_schema: true
 ---
 
 In today’s fast-paced digital landscape, organizations are increasingly adopting platform engineering to optimize their software delivery and operations. Gartner predicts that by 2026, 80% of large software engineering organizations will have platform engineering teams to provide reusable services, components, and tools for application delivery. Additionally, by 2027, 80% of large enterprises will leverage platform engineering to scale DevOps initiatives in hybrid cloud environments effectively.

diff --git a/content/blog/why-switch-to-pulumi/index.md b/content/blog/why-switch-to-pulumi/index.md
@@ -13,6 +13,7 @@ category: general
 social:
     twitter: Why should you switch to Pulumi? This blog post runs through all the reasons by use case, by alternatives, and by benefits.
     linkedin:
+faq_schema: true
 ---
 
 {{< notes type="info" >}}
-Original file line number
+Diff line change
@@ Expand Up / @@ -27,6 +27,7 @@ social: @@
         Whether you're just starting or looking to refine your Kubernetes setup, these insights will help you navigate the complexities and harness the full power of Kubernetes.
         <link>
+    faq_schema: true
     ---
     **Kubernetes best practices** are the production-tested rules that keep clusters reliable, secure, and affordable: set resource requests and limits on every container, isolate workloads with namespaces and NetworkPolicies, enforce least-privilege RBAC, automate health checks, ship via GitOps, validate every change with policy-as-code, generate an SBOM for every image, and manage Kubernetes itself with infrastructure as code instead of hand-rolled YAML. The 20 practices below cover what production teams actually do in 2026 — not what tutorials suggest.
@@ Expand Down @@