From the course: Kubernetes: Service Mesh with Istio

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Solution: Testing a new release

Solution: Testing a new release - Kubernetes Tutorial

From the course: Kubernetes: Service Mesh with Istio

Start my 1-month free trial

Solution: Testing a new release

“

(jingling music) - [Instructor] In solving for the Canary deployment to version three solution, in our modules directory here, we have the three files that I recommended changing, and I've already changed them, so we can look at the host name file first. This describes the deployment for our application, and this has basically everything that was V two has been changed to V three. The name is important just because it separates it from the other deployment names. The label here, the template metadata label version V three is important because that's what links it to the virtual service, and through the destination rule, and then our container as well, so this container image exists, host name version three. This is in docker hub, and it provides a version three of our application, so it would actually spit out a v three if we asked for the versions endpoint. If we do an L-S again, we can also look at our host name, virtual service file, we'll do more on that. I just pasted it in…

Contents