Recap

In this lab, we have set up a demo application with Istio and Argo Rollouts. We have seen how to install Istio in a Kubernetes cluster, enable mTLS and authorization, and expose the application using the Istio Ingress Gateway. We have also seen how to migrate existing Deployments to Argo Rollouts and perform a canary deployment. This demonstrates the benefits of using a service mesh and a deployment tool like Argo Rollouts to manage deployments in a Kubernetes environment.

From here, you can explore more advanced features of Istio and Argo Rollouts, such as traffic mirroring, A/B testing, and automatic rollbacks. You can also explore other service meshes and deployment tools to find the best fit for your use case. Furthermore, it would also be possible to achieve traffic routing based on HTTP headers, which would allow you to route traffic based on user identity or other criteria.

Cleanup

To clean up the resources created in this lab, you can delete the learning-tracker and trusted namespaces using the following commands:

kubectl delete namespace learning-tracker
kubectl delete namespace trusted

To uninstall Istio, you can use the following command:

istioctl uninstall --purge -y
kubectl delete namespace istio-system

If you spun up the cluster only for this lab, you can delete the entire cluster. If you used a managed Kubernetes service, you can delete the cluster using the respective command or UI of your cloud provider.