Guy Daich
Guy Daich
+1 Curious about the use case: cluster-external service?
Question: Do we prefer to have EG generate the cluster and the extension server mutate it? This way, we have better control over naming of clusters (impacting metrics, collisions), linking...
>There's actually [code](https://github.com/envoyproxy/gateway/blob/main/internal/gatewayapi/backend.go#L65) in the Backend translation that should have prevented this backend from being accepted. I believe that users can still use this technique by setting an FQDN endpoint...
+1 for exposing the parser. Use cases: - pre-validation of rules - creating a manifest of ruleset contents which makes it easier to manage modifications (e.g. changes and removals by...
> I am inclined to export the parse but I would expect to have implementation code using this. Do you mean like the example in the PR that you referred...
Hi @jcchavezs, @s3rj1k, Thanks for taking my interest under consideration. The use case I had in mind for exposing the rules is to be able to allow end-users to interact...
Should we maybe turn `RemoteJWKS` to a proper backend reference and then use `BackendTLSPolicy` here?
@arkodg, @patrostkowski My question here would be: In case of a non-transient error, we will still store inconsistent resources (partial? invalid?) that may lead to corruption of XDS. Is there...
Notes from the community meeting: - Provider layer should publish an accurate state-of-the-world. - If transient errors make it impossible to build an accurate snapshot, the reconciliation should be retried...