John Howard
John Howard
you *can* use the chart as a child chart today - you don't *need* to use global. And it really sucks that helm doesn't provide a way to actually properly...
We have an order defined,so it's just the ordering is t ideal (?)
You will never be able to derive a proper Istio CRD from a Go struct, or at least not with kubebuilder. We have completely custom definition (protobuf) -> CRD schema....
That is very interesting. In sidecar, the inbound side basically downgrades it... _sometimes_, depending on the config. If it didn't have a sidecar (consider egress), if it was not configured...
I think this is done and tested in TestSimpleHTTPSandwich
Ah sorry I didn't realize this was for client verification. Are you trying to use Gateway API or IstioGateway? If GWAPI then [frontendValidation](https://gateway-api.sigs.k8s.io/reference/spec/#frontendtlsvalidation) is prob the way to go
integ-ambient-owned-cni_istio is not related to this, separate issue . will review the rest :+1:
> I think that making that change in validation could resolve this ambiguity, and even without validation, making this change to the spec would let implementations refuse rewrites that are...
This is accurate and not really a bug-in-implementation, its simply not implemented at all. So this is probably a feature request I suppose. It may help to understand a bit...
Either I am misunderstanding the issue, or you may be misunderstanding how the probes work, as this doesn't align with my understanding. We have a readiness probe. Readiness probe means...