Alexander Kukushkin

Yeah... Spilo currently discards all Patroni environment variables because it is relying on its own. The `get_dcs_config()` function should be a bit changed so it handles `KUBERNETES_*` env variables similarly...

> ERROR we don't have any running pod and endpoints in this ip 10.233.64.4 And? How this is the Spilo issue?

Spilo only supports backing up to the S3/GCS/Azure and similar that provided by wal-e/wal-g. wal-g also supports backups to the local storage (WALG_FILE_PREFIX), therefore in theory Spilo could be extended...

Please execute `crontabl -l -u postgres` and be surprised.

How long does the build take?

Sorry, but no

Currently build takes about 10 minutes and it is already a bit too much. We can't afford waiting/wasting hours just because of plv8, which seems to be not many people...

> It seems that the Spilo Pods are started as the Root user Yes, this true, but in fact this is more like a fake root, it is limited by...

@Sudeepta92 let's step back and explain what problem are you trying to solve? The thing is that **recovery_target_timeline** has only very narrow use: https://www.postgresql.org/docs/current/continuous-archiving.html#BACKUP-TIMELINES > The default behavior of recovery...

> you can specify that there should be no prefix and suffix within the archive location path (S3), which leads to a location which only holds the cluster name and...