-
Notifications
You must be signed in to change notification settings - Fork 94
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
Add API gateway conformance tests #2403
Comments
Progress update: |
Progress update: |
Above are done. Now there is a issue with not envoyproxy xds being updated. I'm checking this now. Edited: |
Working on enabling ext_authz filter engagement for apis. subtasks:
Update: Handed over to Tharsanan as this conflicts with his work |
Update:
|
Issue : Currently operator created gateway deployments dont get deleted when helm uninstalled.
update: we can use "helm.sh/hook": pre-delete job to execute the manual deletion. |
Currently working on these tasks
|
Update: started working on
|
Update:
|
Started working on following
|
Update:
|
The following tasks are remaining
|
The following issues were found in PR tests Issue 1
Investigations -Sometimes none of the apis get reconciled in adapter. This is not happening when webhooks are disabled, so it can be narrowed down to api webhooks. Observations -router is not ready Issue 2
Issue 3
Observations -Some system apis give 404.
|
Code review suggestions:
|
Problem
Conformance test setup is failing for apk gateway. If we are adhering to gateway spec, their Conformance test should pass. Currently eventhough we support these CRDs, they are not supporting some gateway spec scenarios listed in https://gateway-api.sigs.k8s.io/guides/simple-gateway/.
Solution
https://docs.google.com/document/d/1fwDWKK_yZ3TXfdcA3vSX4Kg_plcg-JBYoobAiwyudtY/edit#heading=h.35yjoemxqx92
Affected Component
Adapter, Enforcer, router
Version
No response
Implementation
Related Issues
No response
Suggested Labels
No response
The text was updated successfully, but these errors were encountered: