envoy: Ubuntu installation fails due to Bintray not being accessible

We saw func-e some days ago, but we weren’t sure how “official” it is or its current status.

I think it is safe to say anything not in the envoyproxy org is not official. https://func-e.io is a Tetrate project and the replacement for what was formerly the getenvoy CLI. Its aim is to make things easier, like before you know what a service mesh or data plane is etc. We intentionally did not replace the system packages as the confusion of the past taught us that lesson!

func-e is decoupled from https://archive.tetratelabs.io/envoy, but is its primary user. This archive is built from the official docker images and the official Homebrew (macOS) packages. In other words, exactly the same binaries as what docker or MacOS installs would produce. This is intentional because we also don’t want confusion as to “who built what” (yet another lesson learned).

It is intentional and for the foreseeable future that https://archive.tetratelabs.io/envoy is used for func-e though #16830 will provide a more official way to get tarballs when implemented. The archive uses permalinks intentionally to get out of the “which package repository is down today” problem which everyone including Tetrate staff were burnt badly by. It is also a way to ensure the least bandwidth is used. For example, debug images are massive, but the archive controls which files have it, etc so that the first timer experience is far more reasonable.

I think it is very related, to mention the above now, but I do think that when the dust settles discussions about Tetrate stuff should be in the appropriate repos, and that will help folks know what is official or not (ex if we are chatting about it here, and it is an envoyproxy thing, it is official!). Meanwhile, I hope this helped!

I spiked this, folks can comment whether to merge it, change it or have me repurpose it to delete the “get envoy” instructions entirely. One way or another, let’s stop advertising broken! https://github.com/envoyproxy/envoy/pull/17246

For anyone needing a temporary workaround (for automated processes or CI not failing), we are temporarily installing Envoy on Ubuntu 18.04 like this (thanks to info in this comment):

ENVOY_VERSION="1.15.5"

# ALTERNATIVE INSTALLATION METHOD
wget https://archive.tetratelabs.io/envoy/download/v${ENVOY_VERSION}/envoy-v${ENVOY_VERSION}-linux-amd64.tar.xz
tar -xf envoy-v${ENVOY_VERSION}-linux-amd64.tar.xz
chmod +x envoy-v${ENVOY_VERSION}-linux-amd64/bin/envoy
sudo mv envoy-v${ENVOY_VERSION}-linux-amd64/bin/envoy /usr/bin/envoy
rm -rf envoy-v${ENVOY_VERSION}-linux-amd64.tar.xz envoy-v${ENVOY_VERSION}-linux-amd64

Thank you very much for that detailed and clarifying explanation! We have a much clearer vision now.