John Howard
John Howard
Use the istio.io/use-waypoint=waypoint label on the service (or namespace). `istioctl waypoint apply --enroll-namespace` also does it for use
This expects the waypoint to be in the same namespace as the service. You can do cross-ns, but its a bit more involved: https://istio.io/latest/docs/ambient/usage/waypoint/#usewaypointnamespace
A string would require a user to write `"true" ` which seems like a regression in user experience and likely source of errors/confusion?
> > A string would require a user to write `"true" ` which seems like a regression in user experience and likely source of errors/confusion? > > Yes, we would...
@JoelSpeed in 99% of cases I would agree to use an enum like this but in this case, given the API we are configuring is `Access-Control-Allow-Credentials: true` (and there is...
> (FWIW I appreciate this is a standard and the likelihood of this changing is close to zero, but, these are the questions I'd be thinking through in any other...
I think it might be confusing to put, on every service "This was not bound to ingress". The user may not even _have_ an ingress at all and we are...
While there is no technical limit, I feel like there is a general budget on how many conditions we can have. If we are over 4 we are doing something...
Yeah or we can deploy 2 waypoint instances instead of merging them
Maybe the cause of https://github.com/istio/istio/issues/37629