Jeff Martin

@connorlwilkes Thank you for your diagnosis on this. Do you know if any progress was made on resolving it? I am experiencing this same issue currently when trying to use...

I believe some of the bugs have been resolved. For example, the NPE when removing a field for a Protobuf schema is no longer an issue as of version `2.2.3.Final`....

Is anyone successfully running PGO with Istio? The first issue I ran into was the backup pod erroring out: ``` % kubectl get pods -n pgo NAME READY STATUS RESTARTS...

This issue is causing one of my team members to move off of VS Code as well. We are using the gRPC protobuf plugin which places generated files here: `target/generated-sources/protobuf/java`....

In looking over the code... I see that the "Could not find a pod with a writable database container." message is likely due to timing of when the role annotations...

Looks like stderr is getting ignored here: https://github.com/CrunchyData/postgres-operator/blob/5286720acb1235cce6d2ed691b6a91de650b014e/internal/controller/postgrescluster/postgres.go#L742 Perhaps this code: ``` // A writable pod executor has been found and we have the sql provided by // the user....

I was able to get this working after adding `\c pgcmain` to my bootstrap script. Adding the additional logging may help to see issues with init more easily... and seems...

Is there a maintainer who would be willing to review the associated PR [here](https://github.com/CrunchyData/postgres-operator/pull/3033)? Thank you in advance.

Is there a maintainer who could review this PR? Thank you in advance.

@cbandy @tjmoore4 @jmckulk Would one of you have a moment to review this PR?