While developing microservices locally is possible, running and testing them in a production-like Kubernetes environment is not easy.
A typical developer workflow or inner loop when developing services in Kubernetes can significantly slow you down - from building a Docker image, pushing it, restarting the deployments, and testing the changes in a shared cluster. And all that, assuming you manage to keep the shared cluster up to date!
In this video, I'll look at a tool called Signadot. Signadot introduces a concept of "sandboxes" that allow you to considerably shorten your developer workflow and go from minutes to mere seconds! The sandbox concept will enable you to build and run a service locally using the upstream and downstream dependencies inside a shared cluster.
Check out the video for a practical demo that shows you how to set everything up and start developing with Signadot.
#Signadot #Kubernetes #microservices #istio
If you like the video, consider subscribing:
/ peterjausovec
▬▬▬▬▬▬ Resources ▬▬▬▬▬▬
▶ Signadot: https://signadot.com
▶ Read the article: https://learncloudnative.com/blog/202...
▬▬▬▬▬▬ Connect with me ▬▬▬▬▬▬
▶ Newsletter: https://learncloudnative.com/newsletter
▶ Twitter: / pjausovec
▶ LinkedIn: / pjausovec
▬▬▬▬▬▬ Contents ▬▬▬▬▬▬
00:00 - Introduction
00:42 - Inner loop/development workflow
02:00 - How about running your service locally?
02:47 - Idea: using Istio to debug apps in Kubernetes
03:26 - Overview of Signadot and sandboxes
04:10 - DEMO: Introduction
04:50 - DEMO: Deploying the sample workloads and going through the inner loop
06:46 - DEMO: Connecting a cluster (Signadot)
07:15 - DEMO: Deploying Signadot operator
07:45 - DEMO: signadot CLI configuration
08:40 - DEMO: Using CLI to connect to the cluster
10:00 - DEMO: Sandbox configuration
11:36 - DEMO: Looking into VirtualService and ServiceEntry configuration
13:42 - Context propagation
14:20 - DEMO: Signadot in action!
16:13 - Signadot use cases
16:49 - Resource plugins
17:40 - Route groups
18:49 - Wrap up