reating both the <code>VirtualServices</code> and <code>DestinationRules</code> that define the corresponding subsets using a single <code>kubectl</code>
call (e.g., <code>kubectl apply -f myVirtualServiceAndDestinationRule.yaml</code> is not sufficient because the
resources propagate (from the configuration server, i.e., Kubernetes API server) to the Pilot instances in an eventually consistent manner. If the
<code>VirtualService</code> using the subsets arrives before the <code>DestinationRule</code> where