Aaron Peschel
Aaron Peschel
It looks like this may be fixed in 855b0d79
The workaround here is to explicitly set AWS_REGION for spilo, rather than let spilo attempt to automatically determine the AWS region.
I'll try to come up with a patch if I have time in the next week or so.
I can see how on one hand how allowing the flexible matching can be see as a benefit, since it means the plugin can be used for project that aren't...
Here's the relevant log lines on the crash. They just match what was already documented in the patroni issue. ``` 2021-12-15 01:05:18,874 INFO: doing crash recovery in a single user...
 It looks like your theory on why the `kill -9` is happening is likely correct. The purple line in this image is...
> Maybe in your case OOM kills not only Patroni but also one or many postgres processes. I tracked the OOM message down in the logs, and can verify this...
@stefanprodan Ah, it should be fine to close this if it's intended. Although, that leaves the question: what is the workflow for adding an overlay with a secret then?
@stefanprodan What is the recommended workflow for setting cluster specific secrets for the reference multi-cluster examples? They seem to rely on overlay patches to set cluster specific values, but if...
One solution I'm seeing is to not use overlays at all, and just fully render the cluster specific resource that needs secrets, eg rather than having a patch, only add...