JVM version (java -version): openjdk 17 2021-09-14 (this is installed with the elastic yum package
OS versionLinux kube-r3-10 3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Description of the problem including expected versus actual behavior:
Elastic correctly respects the proxyPort variables, but does not respect the nonproxyHost variables.
Issue
The repository-s3 plugin fails to work if the S3 bucket can not be reached via the proxy.
This could be remedied by accepting the standard nonproxyHost variable.
Environment
Our elastic cluster can only reach the internet via our proxy.
So we include all the proxyPort variables ES_JAVA_OPTS, including nonproxyHost (in hope)
Our proxy will not connect to internal infrastructure for security reasons.
We have a minio server running inside the network.
7.15.2
repository-s3
java -version
):openjdk 17 2021-09-14
(this is installed with the elastic yum packageLinux kube-r3-10 3.10.0-1160.el7.x86_64 #1 SMP Mon Oct 19 16:18:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Description of the problem including expected versus actual behavior:
Elastic correctly respects the proxyPort variables, but does not respect the nonproxyHost variables.
Issue
The repository-s3 plugin fails to work if the S3 bucket can not be reached via the proxy. This could be remedied by accepting the standard
nonproxyHost
variable.Environment
Steps to reproduce:
Any activity destine for our minio server
Provide logs (if relevant):
logs
there is no traffic sent to minio.int but we do see traffic heading to our proxy
Tcpdump
Squid logs