In last days I had severe trouble configuring Istio due to subtle configuration issues. One of them was providing matching rules in VirtualService where I did not use a list, just single mapping. Another one was DestinationRule where I indented trafficPolicy so that it wasn’t under spec but on root level. These are hard to spot and troublesome to debug. In the latter case the
istioctl validate did not produce any warning.
What kind of validation does Istio do on the custom data types? Could it do more, failing my
kubectl/oc apply with a proper message?