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.

Pulumi Community

hey <@U02681DCL1G> getting some answers for you here
cc <@U017TPA7FEW>

&gt; Does the PKO support checking out the head of branches, rather than specific commits - i.e. follow master
We added support for this in <https://github.com/pulumi/pulumi-kubernetes-operator/blob/master/CHANGELOG.md#0015-2021-07-23>

to track a branch you need to specify things in this format: `refs/heads/master`

<https://github.com/pulumi/pulumi-kubernetes-operator/blob/master/pkg/apis/pulumi/v1alpha1/stack_types.go#L99>

&gt;  Does PKO support local state management, rather than operating against the Pulumi API?
You can specify the backend to use - defaults to pulumi service. See <https://github.com/pulumi/pulumi-kubernetes-operator/blob/master/pkg/apis/pulumi/v1alpha1/stack_types.go#L32>

Our docs are quite lacking on some of these configuration options. Happy to take PRs on example configuration etc.

As soon as I get it working, I’m happy to raise a few!

<@U017TPA7FEW> When attempting to build a python stack from the k8s operator, I seem to be having problems with venv: {“level”:“debug”,“ts”:1628722742.816751,“logger”:“controller_stack”,“msg”:“Pip Install”,“Request.Namespace”:“default”,“Request.Name”:“bow-poc”,“Path”:“/usr/local/bin/python3”,“Args”:[“/usr/local/bin/python3”,“-m”,“venv”,“venv”],“Text”:“Error: [Errno 13] Permission denied: ‘/venv’“} &lt;-- deployments seem to work against other runtimes, i.e. npm.

<@U02681DCL1G> that looks like a filesystem error, python is trying to create your venv at the root of your filesystem `/venv` which probably doesn't have perms

<@UCWG26BH7> This is inside the Pulumi K8s Operator Pod (PKO). It looks like it runs as non-root user, and yes… it does not have permission to create /venv. My feeling is that PKO should either attempt to create the directory within the workspace (which seems to be in /tmp/&lt;tmp-git-checkout-dir&gt;, or in its home directory… the former makes more sense. I’m assuming all that needs doing is to prefix workspace directory to venv before attempting to build out. The other issue I saw was that python attempts to run pip -r, but is unable to find the requirements.txt file… I’m assuming both issues occur due to not CWDing into correct workspace.

Hey Garron. this is related to python inside your env, not Pulumi itself. can you open an iossue on the operator repo for this?

Sorry missed this. Could you open an issue as Lee mentioned?