Review evidence — pulumi/docs #22439

Verification trail

#1 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:45

The guestbook-all-in-one.yaml file contains a comment suggesting switching the redis-master image to the official `redis` image.

framing: The source comment "# or just image: redis" offers an alternative image, and the claim describes it as a suggestion to switch to the official redis image.…; evidence: In kubernetes/examples web/guestbook/all-in-one/guestbook-all-in-one.yaml, the redis-master Deployment's container line is "image: registry.k8s.io/redis:e2e # or just image: redis". That inline comment offers the official `redis` image…; source: https://github.com/kubernetes/examples/blob/master/web/guestbook/all-in-one/guestbook-all-in-one.yaml

source: https://github.com/kubernetes/examples/blob/master/web/guestbook/all-in-one/guestbook-all-in-one.yaml

framing: exact-match — The source comment "# or just image: redis" offers an alternative image, and the claim describes it as a suggestion to switch to the official redis image. That is a fair paraphrase.

pass3 · behavior · high confidence

#2 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:48

The command `sed -i.bak 's|registry.k8s.io/redis:e2e|redis|' guestbook-all-in-one.yaml` replaces the redis-master image with the official `redis` image in…

framing: The sed command's behavior is standard. The upstream manifest confirms that the target string exists and only matches the redis-master image.; evidence: The upstream kubernetes/examples guestbook-all-in-one.yaml has the redis-master container set to "image: registry.k8s.io/redis:e2e # or just image: redis". That string appears only once, on the redis-master line; the replica uses…; source: https://github.com/kubernetes/examples/blob/master/web/guestbook/all-in-one/guestbook-all-in-one.yaml

source: https://github.com/kubernetes/examples/blob/master/web/guestbook/all-in-one/guestbook-all-in-one.yaml

framing: exact-match — The sed command's behavior is standard. The upstream manifest confirms that the target string exists and only matches the redis-master image.

pass3 · behavior · high confidence

#3 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:51

The Pulumi program uses `ConfigFile` to read the guestbook YAML file and provision the resources inside it.

framing: I skipped the cited pulumi/pulumi#25222 because it covers the engine repo, not this claim. The SDK docstring says ConfigFile "creates a set of Kubernetes…; evidence: In every language, the page's example program creates a `yaml/v2` `ConfigFile` with `file: "guestbook-all-in-one.yaml"`. The pulumi-kubernetes SDK confirms what that resource does: "ConfigFile creates a set of Kubernetes resources from a…; source: gh api repos/pulumi/pulumi-kubernetes/contents/sdk/nodejs/yaml/v2/configFile.ts; repo:content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md L53-186

source: gh api repos/pulumi/pulumi-kubernetes/contents/sdk/nodejs/yaml/v2/configFile.ts; repo:content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md L53-186

framing: exact-match — I skipped the cited pulumi/pulumi#25222 because it covers the engine repo, not this claim. The SDK docstring says ConfigFile "creates a set of Kubernetes resources from a ... Kubernetes YAML file", and the claim says it reads "that YAML…

pass1 · behavior · high confidence

#4 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:90

The Go example uses `yamlv2.NewConfigFile` with `yamlv2.ConfigFileArgs` from `github.com/pulumi/pulumi-kubernetes/sdk/v4/go/kubernetes/yaml/v2`.

evidence: I checked pulumi-kubernetes master, `sdk/go/kubernetes/yaml/v2/configFile.go` (package v2, module `sdk/v4`). It defines `func NewConfigFile(ctx *pulumi.Context, name string, args *ConfigFileArgs, opts ...pulumi.ResourceOption)` and `type…; source: gh api repos/pulumi/pulumi-kubernetes/contents/sdk/go/kubernetes/yaml/v2/configFile.go

source: gh api repos/pulumi/pulumi-kubernetes/contents/sdk/go/kubernetes/yaml/v2/configFile.go

framing: exact-match

pass1 · api-surface · high confidence

#5 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:109

The C# examples need `using Pulumi.Kubernetes.Types.Inputs.Yaml.V2;` to use ConfigFileArgs/ConfigGroupArgs from the pulumi-kubernetes C# SDK.

framing: The cited pulumi/pulumi#25222 doesn't cover this claim, so I checked pulumi-kubernetes source directly.; evidence: In pulumi-kubernetes sdk/dotnet/Yaml/V2/ConfigFile.cs, `ConfigFileArgs` sits in `namespace Pulumi.Kubernetes.Types.Inputs.Yaml.V2`, not in `Pulumi.Kubernetes.Yaml.V2` where the resource class lives. The SDK's own example also includes…; source: gh api repos/pulumi/pulumi-kubernetes/contents/sdk/dotnet/Yaml/V2/ConfigFile.cs

source: gh api repos/pulumi/pulumi-kubernetes/contents/sdk/dotnet/Yaml/V2/ConfigFile.cs

framing: exact-match — The cited pulumi/pulumi#25222 doesn't cover this claim, so I checked pulumi-kubernetes source directly.

pass1 · api-surface · high confidence

#6 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:109

The C# namespace `Pulumi.Kubernetes.Types.Inputs.Yaml.V2` exists in the Pulumi Kubernetes SDK and is needed for ConfigFileArgs/ConfigGroupArgs.

framing: The cited pulumi/pulumi#25222 isn't about this namespace, so I checked the pulumi-kubernetes SDK source instead.; evidence: In pulumi-kubernetes master, sdk/dotnet/Yaml/V2/ConfigGroup.cs (base64-decoded) has "namespace Pulumi.Kubernetes.Types.Inputs.Yaml.V2 { public class ConfigGroupArgs : global::Pulumi.ResourceArgs". The constructor takes…; source: gh api repos/pulumi/pulumi-kubernetes/contents/sdk/dotnet/Yaml/V2/ConfigGroup.cs

source: gh api repos/pulumi/pulumi-kubernetes/contents/sdk/dotnet/Yaml/V2/ConfigGroup.cs

framing: exact-match — The cited pulumi/pulumi#25222 isn't about this namespace, so I checked the pulumi-kubernetes SDK source instead.

pass1 · api-surface · high confidence

#7 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:188

Running `pulumi up` on the ConfigFile guestbook program creates the Stack, a `kubernetes:yaml/v2:ConfigFile` named guestbook, and Deployments and Services…

evidence: The yaml/v2 ConfigFile provider registers a component and, when no resourcePrefix is given, uses the ConfigFile's name as the prefix for its child resources: "if !hasResourcePrefix { // use the name of the ConfigFile as the resource…; source: gh api repos/pulumi/pulumi-kubernetes/contents/provider/pkg/provider/yaml/v2/configfile.go

source: gh api repos/pulumi/pulumi-kubernetes/contents/provider/pkg/provider/yaml/v2/configfile.go

pass1 · behavior · medium confidence

#8 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:204

Running `pulumi up` on the ConfigFile guestbook example creates 8 resources.

framing: The cited pulumi/pulumi#25222 is an engine read/dependsOn change and doesn't cover this claim. The count comes from the YAML objects plus the Stack and the…; evidence: The upstream guestbook-all-in-one.yaml has 6 objects: Services and Deployments for redis-master, redis-replica, and frontend. Adding the Stack and the ConfigFile component gives 8, which matches the "+ 8 created" summary and the 8 rows…; source: gh api repos/kubernetes/examples/contents/web/guestbook/all-in-one/guestbook-all-in-one.yaml

source: gh api repos/kubernetes/examples/contents/web/guestbook/all-in-one/guestbook-all-in-one.yaml

framing: The cited pulumi/pulumi#25222 is an engine read/dependsOn change and doesn't cover this claim. The count comes from the YAML objects plus the Stack and the component, not from actually running the program.

pass1 · numerical · medium confidence

#9 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:207

`ConfigFile` exposes the objects it creates through its `resources` output.

framing: The claim applies to yaml/v2 ConfigFile, the type used in the page's examples.; evidence: The generated SDK for kubernetes:yaml/v2:ConfigFile, which is the class the page uses, declares the output "Resources created by the ConfigFile." as `declare public /*out*/ readonly resources: pulumi.Output<any[]>;`. The class has no…; source: gh api repos/pulumi/pulumi-kubernetes/contents/sdk/nodejs/yaml/v2/configFile.ts

source: gh api repos/pulumi/pulumi-kubernetes/contents/sdk/nodejs/yaml/v2/configFile.ts

framing: exact-match — The claim applies to yaml/v2 ConfigFile, the type used in the page's examples.

pass1 · api-surface · high confidence

#10 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:207

`ConfigFile` (yaml/v2) doesn't provide a way to look up a single object by kind and name (no `getResource` helper).

framing: The cited pulumi/pulumi#25222 wasn't needed. The claim was settled directly from the pulumi-kubernetes SDK source.; evidence: The generated yaml/v2 ConfigFile class in the Node.js SDK only exposes `isInstance` and one output, `declare public /*out*/ readonly resources: pulumi.Output<any[]>;`. There is no `getResource` method or any other lookup by kind and…; source: gh api repos/pulumi/pulumi-kubernetes/contents/sdk/nodejs/yaml/v2/configFile.ts

source: gh api repos/pulumi/pulumi-kubernetes/contents/sdk/nodejs/yaml/v2/configFile.ts

framing: exact-match — The cited pulumi/pulumi#25222 wasn't needed. The claim was settled directly from the pulumi-kubernetes SDK source.

pass1 · feature · high confidence

#11 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:210

`kubectl get service frontend` shows the guestbook frontend Service as type NodePort with a cluster IP and port mapping 80:31533/TCP.

evidence: The upstream guestbook frontend-service.yaml (kubernetes.io/examples/application/guestbook/frontend-service.yaml) creates a NodePort Service on port 80. Third-party output for it shows "frontend NodePort 10.96.165.194 <none>…; source: https://docs.ezmeral.hpe.com/runtime-enterprise/57/reference/kubernetes/using-kubernetes/general-functionality/tutorials/general/Kubernetes_Cluster_Usage_Examples.html; intuition: The specific node port 31533 and the cluster IP are example output that changes on every run. Only the Service type…

source: https://docs.ezmeral.hpe.com/runtime-enterprise/57/reference/kubernetes/using-kubernetes/general-functionality/tutorials/general/Kubernetes_Cluster_Usage_Examples.html

pass3 · behavior · medium confidence

#12 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:217

`ConfigGroup` accepts a `files` parameter containing a list of file paths, file globs, and/or URLs, prefixes auto-generated resource names with the…

framing: The cited pulumi/pulumi#25222 doesn't cover ConfigGroup, so I skipped it.; evidence: A code search of pulumi-kubernetes found `resourcePrefix` defined in provider/pkg/gen/overlays.go (where the yaml/v2 schema lives) and in the ConfigGroup templates ("ResourcePrefix is an optional prefix for the auto-generated resource…; source: gh search code --repo pulumi/pulumi-kubernetes resourcePrefix path:provider/pkg/gen

source: gh search code --repo pulumi/pulumi-kubernetes resourcePrefix path:provider/pkg/gen

framing: The cited pulumi/pulumi#25222 doesn't cover ConfigGroup, so I skipped it.

pass1 · api-surface · medium confidence

#13 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:229

The command `sed -i.bak 's|registry.k8s.io/redis:e2e|redis|' yaml/redis-master-deployment.yaml` switches the redis-master Deployment to the official `redis`…

framing: I confirmed the image string from the localized (/ja/) copy of the upstream manifest. The /en/ URL is the inferred canonical address and the example YAML is…; evidence: The upstream Kubernetes guestbook redis-master-deployment.yaml (Deployment `redis-master`) sets `image: registry.k8s.io/redis:e2e # or just image: redis`. That means the sed substitution `s|registry.k8s.io/redis:e2e|redis|` swaps in the…; source: https://raw.githubusercontent.com/kubernetes/website/release-1.33/content/en/examples/application/guestbook/redis-master-deployment.yaml (found via WebSearch on the /ja/ copy; I didn't fetch the /en/ URL)

source: https://raw.githubusercontent.com/kubernetes/website/release-1.33/content/en/examples/application/guestbook/redis-master-deployment.yaml (found via WebSearch on the /ja/ copy; I didn't fetch the /en/ URL)

framing: I confirmed the image string from the localized (/ja/) copy of the upstream manifest. The /en/ URL is the inferred canonical address and the example YAML is normally identical across locales.

pass3 · behavior · medium confidence

#14 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:235

The Pulumi program uses `ConfigGroup` to read the YAML files and provision the resources inside them.

framing: I didn't check the cited pulumi/pulumi#25222 because the provider source settled the claim. The HCL sample (L355-376) was cut off in the grep output, so I…; evidence: Every language sample after L235 uses `yaml.v2.ConfigGroup` with `files: ["yaml/*.yaml"]`. In the provider source, ConfigGroupArgs has `Files pulumi.StringArrayInput \`pulumi:"files"\``. Construct runs "Parse the YAML files and literals…; source: gh api repos/pulumi/pulumi-kubernetes/contents/provider/pkg/provider/yaml/v2/configgroup.go

source: gh api repos/pulumi/pulumi-kubernetes/contents/provider/pkg/provider/yaml/v2/configgroup.go

framing: exact-match — I didn't check the cited pulumi/pulumi#25222 because the provider source settled the claim. The HCL sample (L355-376) was cut off in the grep output, so I didn't confirm that one.

pass1 · behavior · high confidence

#15 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:277

`yamlv2.NewConfigGroup` in the Pulumi Kubernetes Go SDK takes `&yamlv2.ConfigGroupArgs{Files: pulumi.StringArray{...}}`.

evidence: The SDK source defines `func NewConfigGroup(ctx *pulumi.Context, name string, args *ConfigGroupArgs, ...)`. `ConfigGroupArgs` has a `Files pulumi.StringArrayInput` field, and `pulumi.StringArray` implements that interface, so…; source: gh api repos/pulumi/pulumi-kubernetes/contents/sdk/go/kubernetes/yaml/v2/configGroup.go (L180-181, L209-211)

source: gh api repos/pulumi/pulumi-kubernetes/contents/sdk/go/kubernetes/yaml/v2/configGroup.go (L180-181, L209-211)

framing: exact-match

pass1 · api-surface · high confidence

#16 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:377

Running `pulumi up` on the ConfigGroup guestbook program creates a `kubernetes:yaml/v2:ConfigGroup` with 8 created resources (Deployments and Services…

framing: The cited pulumi/pulumi#25222 was not checked. The claim was verified directly against the pulumi-kubernetes ConfigGroup source.; evidence: In pulumi-kubernetes, the yaml/v2 ConfigGroup parses all files with `Parse(ctx.Context(), parseOpts)` and registers each object using `ResourceOptions: []pulumi.ResourceOption{pulumi.Parent(comp)}`, so every object is a direct child and…; source: gh api repos/pulumi/pulumi-kubernetes/contents/provider/pkg/provider/yaml/v2/configgroup.go

source: gh api repos/pulumi/pulumi-kubernetes/contents/provider/pkg/provider/yaml/v2/configgroup.go

framing: exact-match — The cited pulumi/pulumi#25222 was not checked. The claim was verified directly against the pulumi-kubernetes ConfigGroup source.

pass1 · behavior · high confidence

#17 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:1105

The TypeScript example uses a `transforms` resource option on `k8s.yaml.v2.ConfigFile` whose callback returns undefined for non-matching resources.

framing: The PR's cited change, pulumi/pulumi#25222 (engine skips reads during preview), has nothing to do with this claim, so I didn't use it.; evidence: The TypeScript example at L1105-1119 passes `{ transforms: [async (args) => { if (...frontend Service) { ... return { props, opts: args.opts }; } return undefined; }] }` to `new k8s.yaml.v2.ConfigFile(...)`, so the description of the…; source: repo:content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md L1105-1119; gh search code --repo pulumi/pulumi "export type ResourceTransform ="; repo:content/docs/iac/concepts/resources/options/transforms.md L32-41

source: repo:content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md L1105-1119; gh search code --repo pulumi/pulumi "export type ResourceTransform ="; repo:content/docs/iac/concepts/resources/options/transforms.md L32-41

framing: The PR's cited change, pulumi/pulumi#25222 (engine skips reads during preview), has nothing to do with this claim, so I didn't use it.

pass1 · api-surface · medium confidence

#18 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:1157

In the Go transform, `args.Props` is a `pulumi.Map` whose `metadata` and `spec` entries can be type-asserted to `pulumi.Map` and mutated to set spec type to…

framing: The cited PR pulumi/pulumi#25222 (engine skipping reads during preview) has nothing to do with transforms, so I checked the SDK source directly. It confirms…; evidence: The Go SDK's sdk/go/pulumi/transform.go defines `ResourceTransformArgs` with `Props Map` ("The original properties passed to the resource constructor") and `ResourceTransformResult{Props Map; Opts ResourceOptions}`, so the top-level part…; source: gh api repos/pulumi/pulumi/contents/sdk/go/pulumi/transform.go; intuition: If nested objects get unmarshaled into a different type (e.g. map[string]interface{} or an Output), the…

source: gh api repos/pulumi/pulumi/contents/sdk/go/pulumi/transform.go

framing: entailed-narrower — The cited PR pulumi/pulumi#25222 (engine skipping reads during preview) has nothing to do with transforms, so I checked the SDK source directly. It confirms `Props Map`. The claim that nested values can be type-asserted is a reasonable…

pass1 · api-surface · medium confidence

#19 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:1164

The Go example uses `pulumi.Transforms` with `pulumi.ResourceTransform` whose function takes `context.Context` and `*pulumi.ResourceTransformArgs`, reads…

evidence: The Go SDK defines `type ResourceTransform func(context.Context, *ResourceTransformArgs) *ResourceTransformResult`, and `ResourceTransformArgs` has a `Props Map` field. Its doc comment says "If the transform returns nil, this indicates…; source: gh api repos/pulumi/pulumi/contents/sdk/go/pulumi/transform.go

source: gh api repos/pulumi/pulumi/contents/sdk/go/pulumi/transform.go

framing: exact-match

pass1 · api-surface · high confidence

#20 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:1214

The C# example uses `ComponentResourceOptions.ResourceTransforms` with a two-argument callback `(args, _)` returning `Task<ResourceTransformResult?>`.

framing: Checked against the pulumi-dotnet SDK source directly. The cited pulumi/pulumi#25222 wasn't needed because this API is already on the default branch.; evidence: The doc's C# example (L1214–1227) does what the claim says, and the .NET SDK backs that usage. `ResourceOptions` (the base class of `ComponentResourceOptions`) has a `List<ResourceTransform> ResourceTransforms` property with a getter, so…; source: gh api repos/pulumi/pulumi-dotnet/contents/sdk/Pulumi/Resources/ResourceTransform.cs; gh api repos/pulumi/pulumi-dotnet/contents/sdk/Pulumi/Resources/ResourceOptions.cs

source: gh api repos/pulumi/pulumi-dotnet/contents/sdk/Pulumi/Resources/ResourceTransform.cs; gh api repos/pulumi/pulumi-dotnet/contents/sdk/Pulumi/Resources/ResourceOptions.cs

framing: exact-match — Checked against the pulumi-dotnet SDK source directly. The cited pulumi/pulumi#25222 wasn't needed because this API is already on the default branch.

pass1 · api-surface · high confidence

#21 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:1214

The C# `ComponentResourceOptions` has a `ResourceTransforms` property accepting `(args, _) => Task<ResourceTransformResult?>` callbacks, where `args.Type`…

framing: The property is defined on the base class ResourceOptions, so ComponentResourceOptions inherits it.; evidence: In pulumi-dotnet, `ResourceOptions` (which `ComponentResourceOptions` inherits from) declares `public List<ResourceTransform> ResourceTransforms`. The delegate is `public delegate Task<ResourceTransformResult?>…; source: gh api repos/pulumi/pulumi-dotnet/contents/sdk/Pulumi/Resources/ResourceOptions.cs and sdk/Pulumi/Resources/ResourceTransform.cs

source: gh api repos/pulumi/pulumi-dotnet/contents/sdk/Pulumi/Resources/ResourceOptions.cs and sdk/Pulumi/Resources/ResourceTransform.cs

framing: entailed-narrower — The property is defined on the base class ResourceOptions, so ComponentResourceOptions inherits it.

pass1 · api-surface · high confidence

#22 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:1249

After running `pulumi up` with the transform, the `frontend` service is updated in place (not replaced) to a load balancer, with 1 updated and 7 unchanged…

framing: The PR's cited source, pulumi/pulumi#25222 (engine skips reads during preview), doesn't cover this claim, so I skipped it. I checked the provider's force-new…; evidence: The pulumi-kubernetes provider forces replacement of a core/v1 Service only when `.spec.clusterIP` (or metadata name/namespace) changes: `"Service": properties{ ".spec.clusterIP", }`. So switching `spec.type` to LoadBalancer is an…; source: gh api repos/pulumi/pulumi-kubernetes/contents/provider/pkg/provider/diff.go; repo:content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md L190-205

source: gh api repos/pulumi/pulumi-kubernetes/contents/provider/pkg/provider/diff.go; repo:content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md L190-205

framing: The PR's cited source, pulumi/pulumi#25222 (engine skips reads during preview), doesn't cover this claim, so I skipped it. I checked the provider's force-new list instead. The sample output itself wasn't reproduced.

pass1 · behavior · medium confidence

#23 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:1264

Once the load balancer is ready, `kubectl get service frontend` shows the service as type LoadBalancer with an external IP address.

evidence: `kubectl get svc` output has TYPE and EXTERNAL-IP columns. A LoadBalancer service shows <pending> until the cloud provider provisions it, and then shows the external address. Baeldung: "the column with the header EXTERNAL-IP shows the…; source: https://www.baeldung.com/ops/minikube-k8s-service-external-ip-pending; https://oneuptime.com/blog/post/2026-02-09-diagnose-loadbalancer-no-ip/view; intuition: On AWS (ELB/NLB), EXTERNAL-IP usually shows a DNS hostname rather than an IP address. The wording is fine for most…

source: https://www.baeldung.com/ops/minikube-k8s-service-external-ip-pending; https://oneuptime.com/blog/post/2026-02-09-diagnose-loadbalancer-no-ip/view

pass3 · behavior · medium confidence

#24 ✅ Verified

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md:1275

The command `curl http://$(kubectl get service frontend -o jsonpath='{.status.loadBalancer.ingress[0].ip}')` retrieves the Guestbook page from the load…

evidence: The "URL" is a shell command substitution, not a fetchable link. The jsonpath `{.status.loadBalancer.ingress[0].ip}` is the standard way to get a LoadBalancer Service's external IP (Istio docs use `kubectl ... get service ... -o…; source: https://istio.io/latest/docs/tasks/traffic-management/ingress/ingress-control/; intuition: On EKS/AWS the ingress has only a hostname, so `.ip` is empty and the curl fails. The guide may want a `.hostname`…

source: https://istio.io/latest/docs/tasks/traffic-management/ingress/ingress-control/

pass3 · url · medium confidence

Findings

No findings.

Editorial stances

Superlative, ranking, or comparative language the diff adds. No verdict — a page's own framing isn't fact-checkable — listed so a reviewer can confirm each is a stance the docs should take.

content/docs/iac/guides/migration/migrating-to-pulumi/from-kubernetes.md L545 Unlike `ConfigFile` and `ConfigGroup` (v2), the Helm V3 `Chart` makes all provisioned resources available via the `getResource` function. comparison · found by llm-atomic, llm-holistic

Investigation log

cross-sibling-reads: 0 of 5 siblings
external-claim-verification: 24 of 24 claims verified (0 unverifiable, 0 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 18 Pass 1, 0 Pass 2, 6 Pass 3 (verified 6, contradicted 0, unverifiable 0).
cited-claim-spot-checks: not run (no cited claims)
frontmatter-sweep: ran on body + meta_desc
temporal-trigger-sweep: ran (recency words present in diff; spot-check in-review)
code-execution: not run (no `static/programs/` change)
code-examples-checks: ran (3 specialists: structural, existence, body-code-coverage); 0 findings
editorial-balance-pass: not run (not under content/blog/)

History

2026-10-22T21:05:59Z 125e8f2
initial review (pending publication)
2026-10-22T21:33:07Z a612f1fb8b
Re-verified a612f1f: sample comments removed, LB hostname note added; no new findings