Hello everyone, I'm new to Pulumi and I'm currently trying to use the Pulumi Operator to deploy the application. I followed the Pulumi Kubernetes Operator Guide. I have two Pulumi index.ts files: 1. Pulumi Operator index.ts: This script is responsible for deploying the Pulumi Kubernetes operator and setting up the required resources, including the operator's role and service account. you can see the code in the attached file. 2. Sample Application index.ts (curl-pod): This script defines a simple Kubernetes deployment of a curl pod. you can see the code in the attached file. I ran the following commands to verify the deployment, but I am facing issues: • kubectl describe stack curl-pod-stack-dev: The stack is listed correctly. and output are in the attached file. • kubectl get deployments --all-namespaces | grep curl-pod: No results. • kubectl logs -f deployment/pulumi-kubernetes-operator-dev -n dev-pulumi-operator | grep curl-pod: No logs found related to the curl-pod application. • kubectl logs -f deployment/pulumi-kubernetes-operator-dev -n dev-pulumi-operator: I see logs related to the operator, but nothing specific about the application. and output are in the attached file. Could you help me identify what might be missing or what steps I should take to ensure the application is properly deployed using the Pulumi Kubernetes Operator?

cc @damp-airline-38442

Hello @bright-rocket-25257. I observe that you're using v1.x of the Operator. We have a v2 currently in beta and we'd love for you to give it a try; see this introductory blog post. On the specific issue that you're experiencing, I believe the issue is that you're installing the Operator in single-namespace mode (note the

WATCH_NAMESPACE

environment variable) into

dev-pulumi-operator

namespace. Meanwhile the Stack object appears to be in the

default

namespace. Take another look at the installation instructions for how to install in a cluster-wide mode. Note that the "v2" Operator supports cluster-wide mode only.

@damp-airline-38442 Thank you for the feedback! I appreciate the suggestion regarding the v2 Operator. I'll definitely take a look at the blog post and try out the new version. Regarding the issue, I see now that the Operator is installed in single-namespace mode, which could be causing the mismatch. I'll review the installation instructions for cluster-wide mode and make the necessary adjustments. Thanks again for pointing that out! I'll try the changes and let you know how it goes.