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.

Sign up for GitHub

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

Jump to bottom

EnvoyGateway v1.0 release readiness criteria #1160

Closed
2 of 13 tasks
arkodg opened this issue Mar 16, 2023 · 6 comments
Closed
2 of 13 tasks

EnvoyGateway v1.0 release readiness criteria #1160

arkodg opened this issue Mar 16, 2023 · 6 comments
Assignees
@arkodg
Labels
no stalebot
Milestone
Backlog

Comments

@arkodg
Copy link
Contributor

arkodg commented Mar 16, 2023 •
edited
Loading

Description:
Tracks everything needed for Envoy Gateway to be reach v1.0 giving users confidence to run it in production

  • Majority API Gateway features implemented and exposed using a stable API. Requires upstream Gateway APIs to be graduated (tracked with The "Road To GA" Project Board kubernetes-sigs/gateway-api#1801)
    • Conformance tests passing for all v1.0 Gateway API upstream features
    • E2E tests written and passing for all extended features
    • 60%-80% code coverage (from unit tests)
  • Day 2 operations in place
    • Install
    • Observability
      • Review logging to make sure we messaging is clear and logs are set to the appropriate verbosity level
    • Triage
    • Upgrade
    • Customizing Envoy Deployments
  • Meets some criteria of performance when used at scale
  • Document everything

When - TBD
@arkodg
Copy link
Contributor Author

arkodg commented Mar 16, 2023

@envoyproxy/gateway-maintainers please feel free to edit this description

@arkodg arkodg changed the title EnvoyGateway v1.0 release EnvoyGateway v1.0 release readiness criteria Mar 16, 2023
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days.

@github-actions github-actions bot added the stale label Apr 15, 2023
@arkodg arkodg added this to the 0.6.0-rc1 milestone Apr 27, 2023
@arkodg arkodg removed the stale label Apr 27, 2023
@github-actions
Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days.

@github-actions github-actions bot added the stale label May 28, 2023
@arkodg arkodg removed the stale label Aug 1, 2023
@arkodg arkodg self-assigned this Aug 10, 2023
@github-actions
Copy link

github-actions bot commented Sep 9, 2023

This issue has been automatically marked as stale because it has not had activity in the last 30 days.

@github-actions github-actions bot added the stale label Sep 9, 2023
@arkodg arkodg modified the milestones: 0.6.0-rc1, Backlog Oct 14, 2023
@github-actions github-actions bot removed the stale label Oct 14, 2023
@danehans danehans mentioned this issue Oct 18, 2023
Merged
@github-actions GitHub Actions
Copy link

This issue has been automatically marked as stale because it has not had activity in the last 30 days.

@github-actions github-actions bot added the stale label Nov 13, 2023
@Xunzhuo Xunzhuo added no stalebot and removed stale labels Nov 13, 2023
@Xunzhuo
Copy link
Member

Xunzhuo commented Nov 29, 2023

Close by #2249

@Xunzhuo Xunzhuo closed this as completed Nov 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@arkodg arkodg

Labels
no stalebot
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
2 participants
@arkodg @Xunzhuo