Skip to content
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.

Get Started with Kubernetes go example fails #3411

Closed
interurban opened this issue Sep 20, 2023 · 1 comment · Fixed by #3412
Closed

Get Started with Kubernetes go example fails #3411

interurban opened this issue Sep 20, 2023 · 1 comment · Fixed by #3412
Assignees
Labels
area/docs Improvements or additions to documentation docs/examples impact/first-48 This bug is likely to be hit during a user's first 48 hours of product evaluation kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed size/M Estimated effort to complete (up to 5 days).
Milestone

Comments

@interurban
Copy link
Collaborator

interurban commented Sep 20, 2023

Problem description

Reported via our docs control, following the go example here : https://www.pulumi.com/docs/clouds/kubernetes/get-started/

Seeing the following error:

quickstart

./main.go:40:42: deployment.Metadata.Elem undefined (type "github.com/pulumi/pulumi-kubernetes/sdk/v4/go/kubernetes/meta/v1".ObjectMetaOutput has no field or method Elem)

error: error in compiling Go: unable to run go build: exit status 1

I was able to repo this issue today.

Suggestions for a fix

@interurban interurban added needs-triage Needs attention from the triage team area/docs Improvements or additions to documentation kind/bug Some behavior is incorrect or out of spec impact/first-48 This bug is likely to be hit during a user's first 48 hours of product evaluation labels Sep 20, 2023
@interurban interurban added this to the 0.94 milestone Sep 20, 2023
@interurban interurban self-assigned this Sep 20, 2023
@interurban interurban removed the needs-triage Needs attention from the triage team label Sep 20, 2023
@rquitales
Copy link
Member

This is an issue that would affect all languages and is due to the provider attempting to grab the status fields after a SSA dry-run during preview stage. The status fields here would obviously be empty during a dry-run apply, which is why it runs into a panic/out of bounds error. We'll need to handle this user journey during preview.

@desteves desteves transferred this issue from pulumi/docs Sep 28, 2023
@github-actions github-actions bot added the needs-triage Needs attention from the triage team label Sep 28, 2023
@desteves desteves moved this from 🔧 In Progress to 💜 Review in Docs 📚 Oct 2, 2023
@mikhailshilkov mikhailshilkov modified the milestones: 0.94, 0.95 Oct 4, 2023
@desteves desteves added size/M Estimated effort to complete (up to 5 days). docs/examples and removed needs-triage Needs attention from the triage team labels Oct 11, 2023
@pulumi-bot pulumi-bot added the resolution/fixed This issue was fixed label Oct 11, 2023
@github-project-automation github-project-automation bot moved this from 💜 Review to 🏁 Done in Docs 📚 Oct 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area/docs Improvements or additions to documentation docs/examples impact/first-48 This bug is likely to be hit during a user's first 48 hours of product evaluation kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed size/M Estimated effort to complete (up to 5 days).
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

5 participants