Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move Envoy to v4alpha #10614

Closed
htuch opened this issue Apr 1, 2020 · 1 comment
Closed

Move Envoy to v4alpha #10614

htuch opened this issue Apr 1, 2020 · 1 comment
Labels
api/v4 Major version release @ end of Q3 2020 help wanted Needs help!

Comments

@htuch
Copy link
Member

htuch commented Apr 1, 2020

#10355 provides v4alpha protos in the API tree, but doesn't migrate Envoy internally to v4apha. We should do this, ideally by Q4. The main challenge here is to perform API boosting and update the shadow generation technique in #10355 to support creation of hidden_envoy_deprecated_* fields in v4alpha that stretch back to v2 (currently they only work back to v3 as of #10355).

@htuch htuch mentioned this issue Apr 1, 2020
@htuch htuch added api/v4 Major version release @ end of Q3 2020 help wanted Needs help! labels Apr 1, 2020
@htuch
Copy link
Member Author

htuch commented Sep 12, 2021

The likely conclusion of #10943 is that v4 will not happen for a long time, so closing this for now, we've already eliminated v4alpha generation.

@htuch htuch closed this as completed Sep 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api/v4 Major version release @ end of Q3 2020 help wanted Needs help!
Projects
None yet
Development

No branches or pull requests

1 participant