This message was deleted.

sparse-intern-71089

06/09/2023, 9:22 PM

This message was deleted.

billowy-army-68599

06/09/2023, 9:39 PM

if you do

helm ls

on the namespace, do you see any releases?

adamant-terabyte-3965

06/09/2023, 9:50 PM

yes, with status

failed

billowy-army-68599

06/09/2023, 9:56 PM

delete that, then try again with the tag

adamant-terabyte-3965

06/09/2023, 10:19 PM

so I tried deleting the failed Helm Release, and got this error:

Helm release "luketest-serve-karpenter-ns/karpenter" was created, but failed to initialize completely. Use Helm CLI to investigate.: failed to become available within allocated timeout. Error: Helm Release luketest-serve-karpenter-ns/karpenter: timed out waiting for the condition

, and then tried tearing down the cluster and building from a clean slate and got the same error?

adamant-terabyte-3965

06/09/2023, 10:25 PM

I'm a little more confused based on this Github issues thread which the code snippet used seems pretty similar and works for them https://github.com/pulumi/pulumi-kubernetes/issues/2334

adamant-terabyte-3965

06/09/2023, 10:46 PM

Hm, so after examining the pod logs for the Karpenter controller there was an error in the

values

field, and after fixing that the image was pulled from the OCI repo so I don't think this is a Pulumi issue, thank you for your help!

87 Views

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.