Request 899932 (accepted)

Overview

Request 899932 accepted

Please see the following ML thread:

https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org/thread/QCQ2U4PPYD2K4X5CV6CCI45QUYQ5AK2O/

Summary: Cilium and Envoy packaging was always problematic and hard to maintain because of Envoy using Bazel buildsystem and bundling lots of dependencies through it.

We tried once "unbundling" them all, but doing so manually resulted in spending weeks on that on each update.

Then we tried to automatize creation of "vendor tarballs", but this automation eventually stopped working for newer Envoy versions.

Since we are already documenting how to use rke2 with MicroOS/Kubic, and rke2 uses container images built from Dockerfiles, using docker.io registry and Github, I would rather stick to rke2's approach.

Created by mrostecki almost 3 years ago
In state accepted

Delete envoy-proxy

Comments for request 899932 7

Michał Rostecki (mrostecki) - almost 3 years ago

author

Please review the following requests together and test them in the same Staging repo:

Dominique Leuenberger (dimstar_suse) - almost 3 years ago

reviewer target maintainer

Needed for cilium-proxy, cilium can't got yet due to kubicd and patterns

Richard Brown (RBrownSUSE) - almost 3 years ago

Unignored: returned to active backlog.

Richard Brown (RBrownSUSE) - almost 3 years ago

wait for patterns-containers checkin

Richard Brown (RBrownSUSE) - almost 3 years ago

Unignored: returned to active backlog.

Richard Brown (RBrownSUSE) - almost 3 years ago

wait for cilium delete checkin

Dominique Leuenberger (dimstar_suse) - almost 3 years ago

reviewer target maintainer

Unignored: returned to active backlog.

Request History

mrostecki created request almost 3 years ago

Please see the following ML thread:

https://lists.opensuse.org/archives/list/kubic@lists.opensuse.org/thread/QCQ2U4PPYD2K4X5CV6CCI45QUYQ5AK2O/

Summary: Cilium and Envoy packaging was always problematic and hard to maintain because of Envoy using Bazel buildsystem and bundling lots of dependencies through it.

We tried once "unbundling" them all, but doing so manually resulted in spending weeks on that on each update.

Then we tried to automatize creation of "vendor tarballs", but this automation eventually stopped working for newer Envoy versions.