Add an example to Canary.

[brendandburns]

@lachie83 @grampelberg @wmorgan

[grampelberg]

Looks great to me. You've got me thinking about whether this is usable for the ingress controllers as well now. Moving the canary definitions out of random annotations to a real resource would be a large improvement.

[slack]

The decoupling is nice, and having explicit Canary resources is great.

For customers to "start" a canary though, wouldn't all clients of the service need to be re-deployed to use the new "canaryable" service name? Is that a non-starter?

[grampelberg]

@slack it really depends on how you're doing the integration. You could just take over the root service and switch its labels around, copying them down to one of the leaf services. That would maintain this crazy simple/awesome implementation.

From the Linkerd side of things, we don't need to do any of that because the sidecar is already on the client side and the sample workflow should work, including fallback for non-mesh traffic.

[slack]

@grampelberg seems reasonable. Let's merge this and the follow up with the rename in #8