DNM: Poc rustformations sidebyside #10677
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR solely serves to illustrate how we could start migrating off of envoy-gloo into using purely envoyproxy/envoy builds while still being able to extend functionality that gloo users used heavily. This approach relies heavily on the new dynamic_modules examples (https://github.com/envoyproxy/dynamic-modules-examples/tree/main/rust)
In order to have old envoy-gloo functionality work side by side for best effect this also includes bumping envoy-gloo to be on an envoy version post 1.33 which has workable dynamic modules.
Note that this exists to be referenced in the upcoming EP where data plane changes will be proposed to promote vendor neutrality and therefore work to not rely on envoy-gloo repository.