-
Notifications
You must be signed in to change notification settings - Fork 911
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
docs: GTW API support changed to Gloo Gateway instead of GloodMesh #3914
Conversation
Signed-off-by: Ian Rudie <ian.rudie@solo.io>
|
I didn't file an issue since this is just a quick typo, please LMK if that is strictly required. I did not add Solo.io to the users lists since we are building things which integrate with the argo ecosystem and I am not aware of any direct production use here. |
Published E2E Test Results 4 files 4 suites 3h 14m 34s ⏱️ For more details on these failures, see this check. Results for commit ad4a521. |
Published Unit Test Results2 278 tests 2 278 ✅ 2m 59s ⏱️ Results for commit ad4a521. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3914 +/- ##
==========================================
+ Coverage 82.69% 82.75% +0.06%
==========================================
Files 163 163
Lines 22886 22886
==========================================
+ Hits 18925 18940 +15
+ Misses 3087 3077 -10
+ Partials 874 869 -5 ☔ View full report in Codecov by Sentry. |
…rgoproj#3914) correct GTW API support to state Gloo Gateway instead of GloodMesh Signed-off-by: Ian Rudie <ian.rudie@solo.io>
…rgoproj#3914) correct GTW API support to state Gloo Gateway instead of GloodMesh Signed-off-by: Ian Rudie <ian.rudie@solo.io>
Checklist:
"fix(controller): Updates such and such. Fixes #1234"
.