We already use twemproxy / nutcracker as a redis proxy on mediawiki app servers but since twemproxy is unmaintained and envoy does support redis proxy protocol is a good opportunity to explore its usage. Sadly packaging envoy is going to be challenging since the build process is a little bit complex involving bazel, luckily we already have a docker image for envoy building
Description
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | • fsero | T202504 Evaluate VMWare's Harbour as a docker registry | |||
Open | None | T212123 Kubernetes clusters roadmap | |||
Open | None | T209271 improve docker registry architecture | |||
Open | None | T215809 Set up a local redis proxy since docker-registry can only connect to one redis instance for caching | |||
Resolved | • fsero | T215810 Package envoy 1.9.X for stretch and use it as redis proxy on docker registry |
Event Timeline
Change 491951 had a related patch set uploaded (by Fsero; owner: Fsero):
[operations/debs/envoyproxy@wikimedia-stretch] Initial debianization for envoyproxy
Change 492254 had a related patch set uploaded (by Hashar; owner: Hashar):
[integration/config@master] Add debian-glue job to operations/debs/envoyproxy
Change 492254 merged by jenkins-bot:
[integration/config@master] Add debian-glue job to operations/debs/envoyproxy
Change 491951 merged by Fsero:
[operations/debs/envoyproxy@wikimedia-stretch] Initial debianization for envoyproxy
Mentioned in SAL (#wikimedia-operations) [2019-02-25T16:17:31Z] <fsero> upload envoy 1.9.0 to stretch-wikimedia T215810
Mentioned in SAL (#wikimedia-operations) [2019-04-08T11:11:56Z] <fsero> upgrading envoy to 1.9.1 T215810
Adding CVE 2019-9900 and CVE 2019-9901 for better searchability, references are https://github.com/envoyproxy/envoy/issues/6434 and https://github.com/envoyproxy/envoy/issues/6435
Change 491951 merged by Fsero:
[operations/debs/envoyproxy@wikimedia-stretch] Initial debianization for envoyproxy