Emil Flink

Also affected by this, though to be fair it is clearly stated in the [documentation for the Terraform Kubernetes provider](https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs#stacking-with-managed-kubernetes-cluster-resources). If I interpret the docs correctly and the official GKE...

Also seeing the same error message with Weave 2.8.1, we are not seeing this behavior in our clusters still running Weave 2.7.0 EDIT: I believe our problems were mostly because...

I think we are seeing this issue with Weave 2.8.1 and Kubernetes v1.19.11 A node will run fine for a long time and then any connection from a pod on...

To be clear the `--s3-endpoint` should be **without** the scheme prefix as that is provided by the `--s3_use_https` flag. This is the problem @8times4 is hitting, but not the problem...

> @nyxi `DSKY_s3_endpoint` is a typo in the issue or in your real configuration? it should be `DFLY_` Typo, sorry for the confusion. Updated the first post.

For me the problem was trying to use `SERVER_IP` and `SERVER_PORT`: ``` SERVER_IP= SERVER_PORT=15000 ``` Reverting this to empty values fixed the issue with segfaults: ``` SERVER_IP= SERVER_PORT= ```

> @nyxi hi, thanks for the issue, could you please show content of the main artipie config yaml and pypi-proxy repository config? Updated the first post with this info. I...

> @nyxi thanks, the problem is last slash in the remote repository url: use `https://pypi.org/simple` instead of `https://pypi.org/simple/` Please, correct the settings for now and we'll fix this bug soon....