David Palau

Hello @kskewes, my experience with this binary "spin_1.14.1-20200818040017_linux_amd64_spin": ``` $ /tmp/spin_1.14.1-20200818040017_linux_amd64_spin --version version 1.15.0 ``` I've testes also with first release of version 1.14 (spin_1.14.0-20191122172818_linux_amd64_spin) and the problem is the...

More logs just in case they help: ``` $ k logs basic-pd-0 Server: 169.254.25.10 Address: 169.254.25.10#53 Name: basic-pd-0.basic-pd-peer.myapp.svc.cluster.local Address: 10.240.113.2 nslookup domain basic-pd-0.basic-pd-peer.myapp.svc.svc success starting pd-server ... /pd-server --data-dir=/var/lib/pd --name=basic-pd-0...

Hello, I've found the root causes of my problem, just for your knowledge. I had a networkpolicy that limit connections to pods from inside the namespace as best practices dictates....

Thanks @yiduoyunQ, realizing this communication channel is needed solved my issue.

Hello Andrew, sorry but java is not a language I feel comfortable with so I'd appreciate it if you could release a corrected version of s3proxy that we could use....

Thanks very much @gaul, looking forward to the new release of s3proxy including this fix.