touch up a few commands so that everything can be run from the root of
the istio-workshop directory (no cd'ing around during the workshop)
Remove double spaces after periods globally.
Reword a few things.
Couple other questions I have after going through it:
Why do we use istio.yaml and not istio-auth.yaml (which sets up the CA and tells Envoy to use mTLS on all in-mesh connections).
Is there a good reason not to use the initializer, and remove the shell scripts that handle istioctl kube-inject'ing the deployments? We can still talk through what kube-inject does, but with the initializer everyone can use regular old kube commands to deploy everything and we can get rid of the shell scripts. I also like dumping the sleeps in those scripts.
I'm seeing the product page UI fail a lot when I first start it up. In particular, it times out a lot. Any idea why?
We should update all the curl commands to either have an http prefix or not, right now there's a mix of both.
The biggest issue though is that all of the mixer stuff in exercises 9 and 10 need to be rewritten using CRDs. In fact, istioctl mixer doesn't even work in 0.2.
Touch up code blocks everywhere:
Remove double spaces after periods globally.
Reword a few things.
Couple other questions I have after going through it:
istio.yamland notistio-auth.yaml(which sets up the CA and tells Envoy to use mTLS on all in-mesh connections).istioctl kube-inject'ing the deployments? We can still talk through what kube-inject does, but with the initializer everyone can use regular old kube commands to deploy everything and we can get rid of the shell scripts. I also like dumping the sleeps in those scripts.httpprefix or not, right now there's a mix of both.The biggest issue though is that all of the mixer stuff in exercises 9 and 10 need to be rewritten using CRDs. In fact,
istioctl mixerdoesn't even work in 0.2.