Question, wondering if anyone knows if Stack envsRef are able to to be used with config maps? The docs appear a bit unclear.

I don't think so; Looking at the code here: [pulumi-kubernetes-operator/pkg/controller/stack/stack_controller.go at master · pulumi/pulumi-kubernetes-operator](https://github.com/pulumi/pulumi-kubernetes-operator/blob/13b81b8b9e84e3e5669edf10b499d3133340bdeb/pkg/controller/stack/stack_controller.go#L1088) it seems like each key value pair in the EnvRef is a single environment variable; you can't ingest a whole config map with this parameter.

Ahh, that is unfort. It was a cool feature with the deprecated envs

Glad to hear you're interested in getting more involved! A good starting point would be filing or commenting on issues in the project for anything that you'd like to see improved. We're just starting into a design for a pretty big overhaul of the operator internally, so I would maybe ask (again, in an issue on the repo) about specific changes you're thinking you might want to contribute so you don't have any collisions. We should have something to share design wise on that effort soon too; I'll try to make sure to flag it for you when it's posted so you can jump in with any feedback.

Yes please , for now I can add an issue for some of the parts I would like to see.

Hey, wanted to let you know that we've started in on this project here: [Epic] Kubernetes Operator Core Functionality Enhancements (PKOv2)· pulumi-kubernetes-operator/586 Feel free to share any thoughts you might have and let me know if you'd like to try a beta version when it's ready (probably in the next couple weeks)

Thank you! - will take a look. One present issue I have noted with v1 Operator. Using kustomizations via FluxCD the stack Resource appears to not finalize.

Thanks for mentioning that; I don't think we've had any other bug reports of that issue, so it might be worth filing it in the repo so we can take a look.