RFC: Multiple release Envoy images

[mattklein123]

I think we need to start thinking about whether every extension in the tree makes it into our official builds. There are multiple reasons for this:

1. Security implications
2. Feature explosion
3. Support burden for service providers trying to support Envoy generically.

I think we can likely do this via shipping multiple images which perhaps equate to "minimal, "kichen sink," etc. This coupled with management server feature discovery could allow for a sane mechanism to support multiple SKUs (also potentially dynamic extensions).

cc community and @envoyproxy/maintainers for comment. We can also discuss this in the community meeting.

[stale]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

[mattklein123]

@htuch should this be folded into #14078?

[htuch]

@mattklein123 I think it's related but not exactly the same. To the extent we're shipping release images, we can do what you describe above with multiple repositories or a single one.

[lizan]

Related to this as well as #14078, drafted #14094 last night to allow enable / disable extension easier, with some possibilities to define flavors.

[mattklein123]

I'm going to collapse this issue into #14078 and we can continue discussion there.