Nikolay Edigaryev

We've also recently improved the Orchard documentation, it is now [available on the Tart's website](https://tart.run/orchard/quick-start/). I'm going to close this for now, feel free to re-open if you have any...

Hello Robin, I'm not yet sure if exposing the VM's IP in the API would be the right way to proceed because we cannot guarantee that this IP will be...

Please check out the new [`0.22.0` release](https://github.com/cirruslabs/orchard/releases/tag/0.22.0), it exposes a new `GET /v1//ip` endpoint that will resolve the actual VM's IP on the worker. Both the controller and workers need...

Hi @ruimarinho 👋 Would it be possible for you to provide a minimally reproducible Kubernetes configuration (YAML's) that triggers 502s? I really think that this would be a much better...

Closing in favor of https://github.com/cirruslabs/orchard/issues/235. I think we can do better and just avoid using two protocols over a single port completely. This means that no port separation will be...

Hi @ruimarinho 👋 Please check out the latest [Orchard `0.27.0` release](https://github.com/cirruslabs/orchard/releases/tag/0.27.0), it now features an option that could keep the communication between the Controller and Workers HTTP/1.1-only, which should help...

Possibly related to https://github.com/grafana/loki/issues/14788.

Hi Niklas 👋 Thanks for your contribution and for taking the time to provide such a details explanation! I appreciate the effort, but I feel the approach might be a...

>At the end of the day this is a design choice and we can go either way. I'm all in for a simpler approach. Also, falling back to a standard...

> 1. pass in the environment variable? For that you may need to extend the `Tart.run()`'s signature slightly to accept an additional `env` argument and append it accordingly here: https://github.com/cirruslabs/tart/blob/f68297097e5f043191b52302fed17f7ff87ce972/integration-tests/tart.py#L24-L32...