Nikoloz Kvaratskhelia

Vault is using a self-signed certificate.

Isn't the `spring.cloud.config.server.vault.ssl.trust-store` property supposed to do just that? You pass it a truststore containing certificates against which Vault's certificate is compared. At least that's how the `spring.cloud.vault.ssl.trust-store` property works...

Yep, here's the stacktrace: [stacktrace.txt](https://github.com/spring-cloud/spring-cloud-config/files/7872671/stacktrace.txt)

@spencergibb As explained above, the `spring.cloud.consul.discovery.query-passing=true` parameter works inconsistently. Is there currently any other way to exclude unhealthy services from gateway load balancing?

This is the error that I'm getting: Error: connect ETIMEDOUT 104.18.164.99:443 

+1

Hi @jeqo, like @martin960 mentioned, running containers as root should be avoided in general. Also, I had a look at your PR and I think this point from @martin960's previous...

+1

Still waiting for a fix for this: https://github.com/spring-cloud/spring-cloud-vault/issues/571