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

Update roadmap for v0.3.0 #695

Merged
merged 3 commits into from
Nov 9, 2022
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 20 additions & 7 deletions docs/latest/design/roadmap.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ Roadmap features and timelines may change based on feedback, community contribut
roadmap item, you're encouraged to attend a community meeting to discuss the details, or help us deliver the feature by
contributing to the project.

`Last Updated: October 2022`
`Last Updated: November 2022`

### [v0.2.0][v0.2.0]: Establish a Solid Foundation

Expand All @@ -34,11 +34,17 @@ contributing to the project.

### [v0.3.0][v0.3.0]: Drive Advanced Features through Extension Mechanisms

- Global Rate Limiting
- AuthN/AuthZ- [Issue #336][336].
- Lets Encrypt Integration
- Support extended Gateway API fields.
arkodg marked this conversation as resolved.
Show resolved Hide resolved
- Support experimental Gateway APIs such as TCPRoute [Issue #643][643], UDPRoute [Issue #641][641] and GRPCRoute [Issue #642][642].
- Establish guidelines for leveragaing Gateway API extensions [Issue #675][675].
- Rate Limiting [Issue #670][670].
- Authentication [Issue #336][336].

### [v0.4.0][v0.4.0]: Manageability and Scale
### [v0.4.0][v0.4.0]: More Advanced Features through Extension Mechanisms

- Allow users to configure xDS Resources [Issue #24][24].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest moving some of the v0.3 deliverables to v0.4. Note that the original v0.3 deliverables were based on a 6-month release cycle.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is my concern too.


### [v0.5.0][v0.5.0]: Manageability and Scale

- Tooling for devs/infra admins to aid in managing/maintaining EG
- Support advanced provisioning use cases (e.g. multi-cluster, serverless, etc.)
Expand All @@ -52,9 +58,16 @@ contributing to the project.
[v0.2.0]: https://github.com/envoyproxy/gateway/milestone/1
[v0.3.0]: https://github.com/envoyproxy/gateway/milestone/7
[v0.4.0]: https://github.com/envoyproxy/gateway/milestone/12
[v0.5.0]: https://github.com/envoyproxy/gateway/milestone/13
[17]: https://github.com/envoyproxy/gateway/issues/17
[24]: https://github.com/envoyproxy/gateway/issues/24
[60]: https://github.com/envoyproxy/gateway/issues/60
[63]: https://github.com/envoyproxy/gateway/issues/63
[64]: https://github.com/envoyproxy/gateway/issues/64
[17]: https://github.com/envoyproxy/gateway/issues/17
[65]: https://github.com/envoyproxy/gateway/issues/65
[63]: https://github.com/envoyproxy/gateway/issues/63
[336]: https://github.com/envoyproxy/gateway/issues/336
[641]: https://github.com/envoyproxy/gateway/issues/641
[642]: https://github.com/envoyproxy/gateway/issues/642
[643]: https://github.com/envoyproxy/gateway/issues/643
[670]: https://github.com/envoyproxy/gateway/issues/670
[675]: https://github.com/envoyproxy/gateway/issues/675