This message was deleted.
s
This message was deleted.
b
hey, this is a few things lined up: - the crds are global resources, and because they're included in helm charts, it causes problems. You can work around it by using a transformation to omit them for subsequent installations. It's actually an issue with helm we have to work around. You can see an example here: https://github.com/pulumi/pulumi-kubernetes/issues/1225#issuecomment-744472386 If this doesn't work for you, let me know which language sdk you're using and I can help you construct one - the reason your namespace is stuck terminating is because (likely, at my best guess) it has a resource in it that relies on a crd. You can work around this by removing the finalizer from the namespace, or checking inside the namespace for a resource that's been created and removing it. I know this is a pain, but again its part of the dependency graph created by k8s. Let me know if you get stuck and I'm happy to hop on a call and help you work around it
I want you to end up being successful, so please DM me and happy to set up some time to work through some of these issues
c
Thanks for the help btw, I worked through my issues after our call and now everything is in Pulumi.