Lev Petrushchak

Same issue here, Kubernetes 1.7.2, no custom parameters I have tried export NETWORK_HOST=0.0.0.0 but still got this in logs: ``` Exception in thread "main" java.lang.IllegalArgumentException: No up-and-running site-local (private) addresses...

Setting `network.host` directly in elasticsearch.yml to `0.0.0.0` fixed problem for me, here are more details https://github.com/pires/docker-elasticsearch-kubernetes/issues/5

The same here, files with the same name but with different timestamp and content are not synced from S3 to local and --delete does not help

I have the same issue ``` ~ $ export NO_PROXY="127.0.0.1/8,169.254.169.254/32" ~ $ export HTTPS_PROXY="http://127.0.0.1:8080" ~ $ export HTTP_PROXY="http://127.0.0.1:8080" ~ $ ~ $ ~ $ litellm --port 4001 --host 127.0.0.1 --telemetry...

According to [httpx documentation ](https://www.python-httpx.org/advanced/transports/#no-proxy-support) `NO_PROXY` should be set like this `export NO_PROXY="all://127.0.0.1,all://169.254.169.254"` but looks like it's ignored by `boto3` as I can see requests still going to `169.254.169.254` in...

Thanks for the response @krrishdholakia These are actually two separate issues. **First** is that I can't specify NO_PROXY with regular CIDR formatted ip address - I have posted steps to...

@adom4311 Thanks! Just want to add - fix is to run `sentinel reset *` on each sentinel but waiting at least 30 seconds between instances Here is the related quote...