-
Notifications
You must be signed in to change notification settings - Fork 117
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Creating changes seems to fail with a panic when checking metadata or annotations #3204
Comments
We also tried with the latest 3.x version which received the same problem. |
Other things tried - removing |
@illegalnumbers could you give a code example of a resource where you've seen this? |
yea i can try to get a better repro in a bit, i need to get my stacks fixed first :) but afterward i will work on having something better here |
@illegalnumbers did you end up constructing a code example? We can't offer much help without a reproduction. |
What happened?
I ran
pulumi preview
with a kubernetes cluster backing it and got a panic stack trace exception that appears to be related to metadata or annotations on a resource. This has happened with two different resources, aNamespacePatch
and aCustomResourceDefinition
. See below for the stack trace.Example
Output of
pulumi about
CLI
Version 3.132.0
Go Version go1.23.1
Go Compiler gc
Plugins
KIND NAME VERSION
resource auth0 3.5.1
resource gcp 6.67.1
resource gcp 5.26.0
resource kubernetes 4.18.0
resource kubernetes 3.30.2
language nodejs 3.132.0-dev.0
resource tls 4.11.1
Host
OS darwin
Version 13.6.7
Arch arm64
This project is written in nodejs: executable='/Users/illegalnumbers/.asdf/shims/node' version='v20.11.0'
resources omitted for privacy
Dependencies:
NAME VERSION
@pulumi/auth0 3.5.1
@types/node 8.10.66
auth0 4.2.0
tslint 6.1.3
@pulumi/gcp 5.26.0
@pulumi/kubernetes 4.18.0
@pulumi/pulumi 3.103.1
@streamnative/pulumi-common 4.2.3
@types/auth0 2.35.11
typescript 3.9.10
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: