Re: Re: Request for updates: EWG call next week

Hi,

I just joined the list and unable to reply to prior mails in the thread.

This is relevant to containers on FreeBSD.

When using containers in complicated setups, you often want a 'service mesh' 
which is a way for containers to reliably talk to each other, and across 
servers.

A common approach for users of consul & nomad is to make use of envoy as a 
sidecar, however envoy is not building on FreeBSD due to BoringSSL 
dependency and other issues.

  Why is Envoy broken on FreeBSD?
  https://gist.github.com/bretton/495707160c046eb29d0d4b447e5a5758

Other approaches are to use nginx reverse proxies as sidecar containers, or 
other solutions like Istio, which is available in Freshports
https://www.freshports.org/sysutils/istio

I don't have a specific point other than it would be nice to have Envoy 
working in ports, or some ideas for solutions for service meshs and containers.

-- 
regards
Bretton