Repository navigation
Fix Kubernetes YAML examples in the migration guide for yaml/v2 - #22439
Conversation
Sentinel — merge gate statusAll gates green — nothing is blocking this merge.
Evaluated at head Need help, or think a gate got it wrong? Ask in |
Reviewer's guide v2 — not for the authorTip Check the PR author: nothing here is yours. Your to-do list is the "Author action guide" comment. Review requested from: @pulumi/docs-guild — an approval from anyone with write access satisfies the merge gate. Note What this PR changes:
A reader would be blocked by code samples that call APIs Review confidence:
|
Author action guide v2 — nothing blocks mergeNote Nothing here needs an answer from you. A human reviewer still approves the merge. This PR removes the Full evidence: verification trail, investigation log, review history. Review v2 · updated 2026-10-22T21:33:07Z · head commit a612f1f Please don't edit or delete this comment; it's the review's record. |
|
Your site preview for commit a612f1f is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-22439-a612f1fb.s3-website.us-west-2.amazonaws.com Changed pages: |
|
/update-review |
Fixes the YAML and transforms examples in the Kubernetes migration guide. #17726 moved them to
yaml/v2but keptgetResource, which v2 doesn't have:packageline. They now only deploy, and the page showskubectl get service frontendto find the cluster IP.redis:e2eimage can't be pulled on containerd 2.1 and later, so every deploy timed out. Added asedstep that switches it toredis, as the file's own comment suggests.Page: https://www.pulumi.com/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes/
I ran every example on minikube in all six languages and checked that the transforms turn the frontend into a load balancer. I tried keeping an IP export with
Service.getanddependsOn, but that only works on CLI v3.271.0 and later (pulumi/pulumi#25222), so I went with kubectl.