Open arkodg opened 7 months ago
I am interested in working on this feature. want to understand which one to prioritize if gateway API enable but we are not enabling it on ClientTraficPolicy?
let me finish #3202 before working on this one
I am interested in working on this feature. want to understand which one to prioritize if gateway API enable but we are not enabling it on ClientTraficPolicy?
@zufardhiyaulhaq we'll need to simultaneously support both fields, until there is complete feature parity in upstream
@arkodg @shawnh2 after checking the spec https://gateway-api.sigs.k8s.io/geps/gep-91/ seems there are no optional features there. which means that if ClientTrafficPolicy set the optional to true, we need to rewrite it to true right?
@arkodg
@zufardhiyaulhaq we'll need to simultaneously support both fields, until there is complete feature parity in upstream
which one to be used if different secret is being used on Gateway object & ClientTrafficPolicy object? do we need to merge the certificate?
yah lets merge/append the caCerts
, this will help with migration in the future
This issue has been automatically marked as stale because it has not had activity in the last 30 days.
This issue has been automatically marked as stale because it has not had activity in the last 30 days.
This issue has been automatically marked as stale because it has not had activity in the last 30 days.
Description:
Support the new Client Cert Validation field introduced by upstream https://gateway-api.sigs.k8s.io/geps/gep-91/
Its the same feature as https://github.com/envoyproxy/gateway/issues/88, and has been implemented in the project using ClientTrafficPolicy, so the translation can be reused
[optional Relevant Links:]