Gabriel

Just make sure that the owner and the group is oracle, is not enought setting 777 permissions

Same issue here, trying to debug the issue I'm getting that it tries to connect to [bucket-name]-dev.s3.wasabisys.com which doesn't seem to be correct. Credentials and policy are correct.

I already did it, and just in case I changed the region to s3.eu-west-1.wasabisys.com but not working either. Do I need any special policy for s3fs? I have this: `{...

Errors received: Connection #1 to host [BUCKET_NAME].s3.wasabisys.com left intact HTTP response code 403, returning EPERM Check bucket failed, S3 response: s3fs.cpp:s3fs_check_service(3502): Failed to connect by sigv4, so retry to connect...

> I successfully connected to Wasabi via: > > ``` > s3fs BUCKET PATH -o profile=PROFILE -o url=https://s3.us-west-1.wasabisys.com > ``` > > Curiously setting the URL to the correct region...

Perfect thanks! I will try to build the spilo image with this.

I successfully built postgres 15 spilo image, but the operator says that the 15 version is not valid and installs 14.4, what should I do? Thanks!

I had to add the version 15 to the enum in the CRD: kubectl edit crd postgresqls.acid.zalan.do  

Any ideas on how can I patch this automatically until this gets done? Maybe I should be able to make a kubectl patch on the CRD? I don't quite control...

I came across with just a cheap and dirty patch but it works meanwhile, drop suport for postgresql replacing by 15: ``` kubectl get crd postgresqls.acid.zalan.do -n "${POSTGRES_OPERATOR_NAMESPACE}" -o yaml...