Liam White

I think I'm seeing the same thing, my errors are: ``` kubernetes:core/v1:ConfigMap hosted-cp-workshop-nodeAccess creating error: configured Kubernetes cluster is unreachable: unable to load schema information from the API server: the...

We are still seeing this but the above workaround doesn't work for us. We manually add it back in and then subsequent updates override it. The only workaround that does...

I am also seeing similar things when trying to rotate keys. I get passphrase incorrect on my root key even though it's definitely correct. ``` notary Version: 0.4.3 Git commit:...

@gmaurelia so I've been doing some more playing around and it seems to work before I run a `notary delete`, but when I try to rotate a key after a...

We have done this both manually and with that command

We end up having to use volumes anyway (I think due to our use of a monorepo). The volume fills up over time as pods are killed mid-reconcile. Obviously, we...

Additionally, we also have to run as root or chmod/chown /tmp. ``` {"level":"debug","ts":1632162989.3121283,"logger":"controller_stack","msg":"NPM/Yarn","Request.Namespace":"pulumi-operator","Request.Name":"...","Dir":"...","Path":"/usr/bin/yarn","Args":["/usr /bin/yarn","install"],"Text":"Error: EACCES: permission denied, open '/tmp/.config/yarn'"} ```

For people who want a quick workaround we use the following docker image: ``` FROM pulumi/pulumi-kubernetes-operator:v0.0.20 # Enable us to use yarn, see https://github.com/pulumi/pulumi-kubernetes-operator/issues/196 USER root RUN npm uninstall npm...

FWIW, we work around this by generating local stack configs using the automation API. This won't solve all use cases though. ```typescript interface StackArgs extends LocalProgramArgs { config: { [key:...

Reading through #2318 I agree that I think it makes sense to build it at a layer above similar to something like [Atlantis](https://www.runatlantis.io/)