Open BarDweller opened 4 years ago
On some investigation, it seems we may have lost the setting of `global.proxy.includeIPRanges' on istio.
This might have an impact to this issue, investigating.
istioctl install --set values.global.proxy.includeIPRanges="10.0.0.1/24"
Where the range itself, for minikube can be determined via
kubectl describe pod kube-apiserver -n kube-system | grep 'service-cluster-ip-range'
Need to figure out what the equiv command is for crc, if any.
As part of the recent upgrades, testing revealed a problem with using room via wss://frontdoor with istio on minikube.
Room has been moved back to ws://internal for now.
Investigate the failure, fix it, and revert room back to wss://frontdoor